Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d575a6b2e3064a5534edb5a106e9766f4ed5bd1efec03f700c782ca05b1f3017

Tx prefix hash: 09b3830ee2ba6232a99c094b0e89649e84783d81a1eb91b7aaa2e8a5bdb23c77
Tx public key: 4adf44f1c762abb827d016773fd1e9bf334bc71d51d4451d299891caffbb7dc0
Timestamp: 1738308309 Timestamp [UCT]: 2025-01-31 07:25:09 Age [y:d:h:m:s]: 00:294:16:56:51
Block: 1208918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208389 RingCT/type: yes/0
Extra: 014adf44f1c762abb827d016773fd1e9bf334bc71d51d4451d299891caffbb7dc00211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a00aec3d0017f4ad5d6850fb4c2226b18a56487b26d84086b310cc6501cdc36 0.600000000000 1695655 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": 1208928, "vin": [ { "gen": { "height": 1208918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a00aec3d0017f4ad5d6850fb4c2226b18a56487b26d84086b310cc6501cdc36" } } ], "extra": [ 1, 74, 223, 68, 241, 199, 98, 171, 184, 39, 208, 22, 119, 63, 209, 233, 191, 51, 75, 199, 29, 81, 212, 69, 29, 41, 152, 145, 202, 255, 187, 125, 192, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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