Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 483fd4c2335fe095d9c32c09992ebddfea1d161b428f497139a31467c8e03933

Tx prefix hash: 53df912819239d045f328197eb9004214124c7cc6500d0fd11f0d4b422fd1c0e
Tx public key: e95ee36dbb6f52e9ce18ef37c2a0bcbff6c3dca0ac11fa0b3c7cdeabbeca9489
Timestamp: 1745543120 Timestamp [UCT]: 2025-04-25 01:05:20 Age [y:d:h:m:s]: 00:217:06:11:55
Block: 1268810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153002 RingCT/type: yes/0
Extra: 01e95ee36dbb6f52e9ce18ef37c2a0bcbff6c3dca0ac11fa0b3c7cdeabbeca948902110000000adbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59f80cf3b9a01e41a09102d29e5a744427484532abad08c375b0d218ce8c544a 0.600000000000 1756043 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": 1268820, "vin": [ { "gen": { "height": 1268810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59f80cf3b9a01e41a09102d29e5a744427484532abad08c375b0d218ce8c544a" } } ], "extra": [ 1, 233, 94, 227, 109, 187, 111, 82, 233, 206, 24, 239, 55, 194, 160, 188, 191, 246, 195, 220, 160, 172, 17, 250, 11, 60, 124, 222, 171, 190, 202, 148, 137, 2, 17, 0, 0, 0, 10, 219, 181, 113, 193, 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