Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88164aa15b8f2dc5e228def0df1223967cff4d48ac0ed08c7146db10619eba22

Tx prefix hash: 0a66080862057dbbd482fbb826ba39c6c9877a58d4723f05d144fe3a3a0aff3e
Tx public key: 5f4a0d1823cc0efc83a0300facef3e6294e4aeee48859de521dcaba03e985b3f
Timestamp: 1762234182 Timestamp [UCT]: 2025-11-04 05:29:42 Age [y:d:h:m:s]: 00:062:20:37:31
Block: 1404575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45014 RingCT/type: yes/0
Extra: 015f4a0d1823cc0efc83a0300facef3e6294e4aeee48859de521dcaba03e985b3f0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7770f42fd261f071be3434ab6f1afce254d4e2a96354a65960f057e10b55ce5e 0.600000000000 1892934 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 dinasty-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": 1404585, "vin": [ { "gen": { "height": 1404575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7770f42fd261f071be3434ab6f1afce254d4e2a96354a65960f057e10b55ce5e" } } ], "extra": [ 1, 95, 74, 13, 24, 35, 204, 14, 252, 131, 160, 48, 15, 172, 239, 62, 98, 148, 228, 174, 238, 72, 133, 157, 229, 33, 220, 171, 160, 62, 152, 91, 63, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8