Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06979df23a8fae0cb8e36d1b5882f8fb64cadf2a73d85af374ed0511b892347b

Tx prefix hash: ae81cd341715795967b934b48dbc19aac3c379a399203f87dc242ff05be1f352
Tx public key: 818fdd74d105c63e1c9cbb21d97d246f9ef10b9a81dc99bd48dba369f3bc808b
Timestamp: 1751882658 Timestamp [UCT]: 2025-07-07 10:04:18 Age [y:d:h:m:s]: 00:143:19:48:37
Block: 1320546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101226 RingCT/type: yes/0
Extra: 01818fdd74d105c63e1c9cbb21d97d246f9ef10b9a81dc99bd48dba369f3bc808b02110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e28ca05513ed223cb3b08262a4123ea4acc73e52c81fbff28cd6bf37e6f1b80a 0.600000000000 1808245 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": 1320556, "vin": [ { "gen": { "height": 1320546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e28ca05513ed223cb3b08262a4123ea4acc73e52c81fbff28cd6bf37e6f1b80a" } } ], "extra": [ 1, 129, 143, 221, 116, 209, 5, 198, 62, 28, 156, 187, 33, 217, 125, 36, 111, 158, 241, 11, 154, 129, 220, 153, 189, 72, 219, 163, 105, 243, 188, 128, 139, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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