Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff4da6c338997057bcd84e4b67d36c066a19e7beb108fa669c3238677de5f1a0

Tx prefix hash: c45e14e847c2095b87ee127547dfc81b923267a7b433509756702f02e332da31
Tx public key: dfb615276abceed96831e4fb1c2a99252d8bee1d0302d3f352b176054333f196
Timestamp: 1712861779 Timestamp [UCT]: 2024-04-11 18:56:19 Age [y:d:h:m:s]: 00:259:20:24:09
Block: 998355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186017 RingCT/type: yes/0
Extra: 01dfb615276abceed96831e4fb1c2a99252d8bee1d0302d3f352b176054333f1960211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5fdad0445c5e64cf46de1c71ba764037d68b31941ed1493d4c50be2d46e8a54 0.600000000000 1458801 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": 998365, "vin": [ { "gen": { "height": 998355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5fdad0445c5e64cf46de1c71ba764037d68b31941ed1493d4c50be2d46e8a54" } } ], "extra": [ 1, 223, 182, 21, 39, 106, 188, 238, 217, 104, 49, 228, 251, 28, 42, 153, 37, 45, 139, 238, 29, 3, 2, 211, 243, 82, 177, 118, 5, 67, 51, 241, 150, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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