Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d283c2e2796a20da86779b726f9aabe35b2b10f1ea8617fbd7446b9442fd2edd

Tx prefix hash: f8423ef1b6b42ad2ba866c16a8dba331e60761b8062e6b3f8cbd4df52c8400d4
Tx public key: 98b7e92a39f53dc49990a8d1529f70c9dda7bd0801f123cb8cc28942295e7d9f
Timestamp: 1763466062 Timestamp [UCT]: 2025-11-18 11:41:02 Age [y:d:h:m:s]: 00:009:20:41:32
Block: 1414786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7053 RingCT/type: yes/0
Extra: 0198b7e92a39f53dc49990a8d1529f70c9dda7bd0801f123cb8cc28942295e7d9f02110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5441c3fde19a1c1109558186f3fd16e77fbc80092bfc69b131f4905431d0a46 0.600000000000 1903279 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": 1414796, "vin": [ { "gen": { "height": 1414786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5441c3fde19a1c1109558186f3fd16e77fbc80092bfc69b131f4905431d0a46" } } ], "extra": [ 1, 152, 183, 233, 42, 57, 245, 61, 196, 153, 144, 168, 209, 82, 159, 112, 201, 221, 167, 189, 8, 1, 241, 35, 203, 140, 194, 137, 66, 41, 94, 125, 159, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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