Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66c4c2caf57993545ca4fddc0e0ceb60cf2e542c3063829ee0bae31df5e63a18

Tx prefix hash: 94b30d29cc86e4e69920b413b4b9d14031524d9066fd793e7828c36b34ce80b8
Tx public key: 4001b387ffa0036a0b79920893e9431fc71214087fd84ac47060e5ab8a19ae7a
Timestamp: 1769082769 Timestamp [UTC]: 2026-01-22 11:52:49 Age [y:d:h:m:s]: 00:298:16:13:07
Block: 1461197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218930 RingCT/type: yes/0
Extra: 014001b387ffa0036a0b79920893e9431fc71214087fd84ac47060e5ab8a19ae7a021100000003215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 639803184a568c29baddfe4a75ceed5c8b6e38c05f3fff14183ac39c934eb816 0.000600000000 1950377 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": 1461207, "vin": [ { "gen": { "height": 1461197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "639803184a568c29baddfe4a75ceed5c8b6e38c05f3fff14183ac39c934eb816" } } ], "extra": [ 1, 64, 1, 179, 135, 255, 160, 3, 106, 11, 121, 146, 8, 147, 233, 67, 31, 199, 18, 20, 8, 127, 216, 74, 196, 112, 96, 229, 171, 138, 25, 174, 122, 2, 17, 0, 0, 0, 3, 33, 91, 191, 137, 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: