Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52e3c3143ce8b388b78d1cefc02fd1a8ae32dad81714910def10a359ec48ce72

Tx prefix hash: 55ac9b5b9fd274436b274f5ace751b012c21b7bfd1ae6a556ae5c39a3ad68593
Tx public key: 0aafd38d9e55e5de895ce3e31a71068416aaad817dccb1feac590b0a5d9edeb4
Timestamp: 1745402808 Timestamp [UCT]: 2025-04-23 10:06:48 Age [y:d:h:m:s]: 00:284:01:54:36
Block: 1267638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200671 RingCT/type: yes/0
Extra: 010aafd38d9e55e5de895ce3e31a71068416aaad817dccb1feac590b0a5d9edeb4021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b99ef42013dfe6e2e1f818eaa01dc16a326c76464103efa402142ed646c3346 0.600000000000 1754867 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": 1267648, "vin": [ { "gen": { "height": 1267638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b99ef42013dfe6e2e1f818eaa01dc16a326c76464103efa402142ed646c3346" } } ], "extra": [ 1, 10, 175, 211, 141, 158, 85, 229, 222, 137, 92, 227, 227, 26, 113, 6, 132, 22, 170, 173, 129, 125, 204, 177, 254, 172, 89, 11, 10, 93, 158, 222, 180, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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