Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55665a3706cb8d23abdbf25095f5dba0e8c581d071dec3c058f832655159cbd4

Tx prefix hash: adfb49dfe7fa490793a799ba01e4157f26079e7075cb479082790ec9a1786984
Tx public key: 1d91c8534ae83c3a3bd208dc1e9b6e1da866a6ffc5f773e07272670290bbfa6e
Timestamp: 1751439313 Timestamp [UCT]: 2025-07-02 06:55:13 Age [y:d:h:m:s]: 00:134:21:50:45
Block: 1317058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94654 RingCT/type: yes/0
Extra: 011d91c8534ae83c3a3bd208dc1e9b6e1da866a6ffc5f773e07272670290bbfa6e021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 956041e1d0ffe7c1fe3088e373cb6b09588ab35094e5e03e056a52661d202e48 0.600000000000 1804723 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": 1317068, "vin": [ { "gen": { "height": 1317058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "956041e1d0ffe7c1fe3088e373cb6b09588ab35094e5e03e056a52661d202e48" } } ], "extra": [ 1, 29, 145, 200, 83, 74, 232, 60, 58, 59, 210, 8, 220, 30, 155, 110, 29, 168, 102, 166, 255, 197, 247, 115, 224, 114, 114, 103, 2, 144, 187, 250, 110, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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