Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 491b11ef192869c9cfbee45ca2542343a2056d0556210e2bcf85dea130821200

Tx prefix hash: 1d13ed78960a3c08d68bfbd13e30f30bf8e07027e99da0cf46462b697e4d1db1
Tx public key: 33bbf96befba3aeda2c2e7b15f335c98fce8dce8d5d64b1fd95bc0be966aa78d
Timestamp: 1590432882 Timestamp [UCT]: 2020-05-25 18:54:42 Age [y:d:h:m:s]: 04:217:22:00:56
Block: 103252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1081887 RingCT/type: yes/0
Extra: 0133bbf96befba3aeda2c2e7b15f335c98fce8dce8d5d64b1fd95bc0be966aa78d0211000001e1ff0e1d7d000000000000000000

1 output(s) for total of 279.179818121000 dcy

stealth address amount amount idx
00: ee2fba531d217ea2195081742f686394014182b1dfefdc5ea5cd59c71fdd63bb 279.179818121000 181157 of 0

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": 103262, "vin": [ { "gen": { "height": 103252 } } ], "vout": [ { "amount": 279179818121, "target": { "key": "ee2fba531d217ea2195081742f686394014182b1dfefdc5ea5cd59c71fdd63bb" } } ], "extra": [ 1, 51, 187, 249, 107, 239, 186, 58, 237, 162, 194, 231, 177, 95, 51, 92, 152, 252, 232, 220, 232, 213, 214, 75, 31, 217, 91, 192, 190, 150, 106, 167, 141, 2, 17, 0, 0, 1, 225, 255, 14, 29, 125, 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