Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b990967a126b95b5d4d518bdf14f350fd1f8f773555beb06d4358d455b74f78

Tx prefix hash: bbb960d33e1f3847a5e53893db1562924b72f249b02463817092a1ed033a368d
Tx public key: 807272be5ca8a9085865d6d3617c071872bdaeb822a9e2d8228d0f935288af1d
Timestamp: 1759849743 Timestamp [UCT]: 2025-10-07 15:09:03 Age [y:d:h:m:s]: 00:044:18:30:55
Block: 1384804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32056 RingCT/type: yes/0
Extra: 01807272be5ca8a9085865d6d3617c071872bdaeb822a9e2d8228d0f935288af1d02110000000597baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc4d58b94f1a63ebfcf9f9fd987199551bcf2b93f0216a27aa10eb8fd15cb966 0.600000000000 1872961 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": 1384814, "vin": [ { "gen": { "height": 1384804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc4d58b94f1a63ebfcf9f9fd987199551bcf2b93f0216a27aa10eb8fd15cb966" } } ], "extra": [ 1, 128, 114, 114, 190, 92, 168, 169, 8, 88, 101, 214, 211, 97, 124, 7, 24, 114, 189, 174, 184, 34, 169, 226, 216, 34, 141, 15, 147, 82, 136, 175, 29, 2, 17, 0, 0, 0, 5, 151, 186, 249, 34, 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