Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf6a9fadde0f1f13dbff425d88b7089d2ae00fe8169fb43e34651e3501b299ed

Tx prefix hash: 64b65359f7509d833b5a3a3e8e6daa5a59d171f69e4003d583fec4a6b4321141
Tx public key: eb476359dd5b9e6e21dd3b502d9c5281cf65d2303d8574a34038892e5e620408
Timestamp: 1751937098 Timestamp [UCT]: 2025-07-08 01:11:38 Age [y:d:h:m:s]: 00:184:16:33:37
Block: 1320965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130524 RingCT/type: yes/0
Extra: 01eb476359dd5b9e6e21dd3b502d9c5281cf65d2303d8574a34038892e5e620408021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04d863463e49562ef549d2e5d0155f5acdb13e70468f2374a83aa20729f53cbf 0.600000000000 1808668 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": 1320975, "vin": [ { "gen": { "height": 1320965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04d863463e49562ef549d2e5d0155f5acdb13e70468f2374a83aa20729f53cbf" } } ], "extra": [ 1, 235, 71, 99, 89, 221, 91, 158, 110, 33, 221, 59, 80, 45, 156, 82, 129, 207, 101, 210, 48, 61, 133, 116, 163, 64, 56, 137, 46, 94, 98, 4, 8, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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