Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45b4b8d1dc62e4a0b4bd168dd16fbb3d5f0f97f1f1d48b20ea8377fe0f844138

Tx prefix hash: dd15da51737cfed8773468c24aaba8fd8754203bd70596b7ab4d26fb5f39fc24
Tx public key: 5bf16b847b212369faeea0fbf42a8ee72c14327df6e464448bb82ab56b30986a
Timestamp: 1772620015 Timestamp [UTC]: 2026-03-04 10:26:55 Age [y:d:h:m:s]: 00:256:08:41:28
Block: 1490435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188667 RingCT/type: yes/0
Extra: 015bf16b847b212369faeea0fbf42a8ee72c14327df6e464448bb82ab56b30986a021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ecdd69f38675b3660e1b8f92738c9b82883689524abfe37588ab1d570fab6c72 0.000600000000 1979937 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": 1490445, "vin": [ { "gen": { "height": 1490435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecdd69f38675b3660e1b8f92738c9b82883689524abfe37588ab1d570fab6c72" } } ], "extra": [ 1, 91, 241, 107, 132, 123, 33, 35, 105, 250, 238, 160, 251, 244, 42, 142, 231, 44, 20, 50, 125, 246, 228, 100, 68, 139, 184, 42, 181, 107, 48, 152, 106, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: