Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 217347de03ebaf983fe3adf45a2cde7ca3b8fd33c87d7002871a09ed9461c97b

Tx prefix hash: 605d969777b54c418a33ae7206c0b782914a8155702e356e65464cc4e04d05cd
Tx public key: f5254de6ecbaf6a2864724844033d4057512e0dd3817545d70a40e96f821f7dd
Timestamp: 1750857136 Timestamp [UTC]: 2025-06-25 13:12:16 Age [y:d:h:m:s]: 01:146:07:08:55
Block: 1312536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368828 RingCT/type: yes/0
Extra: 01f5254de6ecbaf6a2864724844033d4057512e0dd3817545d70a40e96f821f7dd021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1beb12a4b97a545ac16b1aadb3988d1a4e7f7fc680ffd683eeb35f38b17a702b 0.000600000000 1800169 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1312546, "vin": [ { "gen": { "height": 1312536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1beb12a4b97a545ac16b1aadb3988d1a4e7f7fc680ffd683eeb35f38b17a702b" } } ], "extra": [ 1, 245, 37, 77, 230, 236, 186, 246, 162, 134, 71, 36, 132, 64, 51, 212, 5, 117, 18, 224, 221, 56, 23, 84, 93, 112, 164, 14, 150, 248, 33, 247, 221, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: