Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3544ed99419dcae1e31f96794722d24ff0262d5c4d3bb2228035c178b4e49fb5

Tx prefix hash: 54e7f92df675574cdce58ec8e66c4ffa4d64de777e8795391e7178ce8021404b
Tx public key: 2e5c94f1ae322bdcddbef4951afa4a3630a3daad1c92b90fb4ca110637d350f2
Timestamp: 1578002560 Timestamp [UCT]: 2020-01-02 22:02:40 Age [y:d:h:m:s]: 05:062:14:26:03
Block: 37448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194502 RingCT/type: yes/0
Extra: 012e5c94f1ae322bdcddbef4951afa4a3630a3daad1c92b90fb4ca110637d350f20211000000064943cd9f000000000000000000

1 output(s) for total of 461.232691602000 dcy

stealth address amount amount idx
00: 2d8dccdb8c1dfde041c3531da7501dbd7acd77bb20df64fbae20d51b137d98a6 461.232691602000 63572 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": 37458, "vin": [ { "gen": { "height": 37448 } } ], "vout": [ { "amount": 461232691602, "target": { "key": "2d8dccdb8c1dfde041c3531da7501dbd7acd77bb20df64fbae20d51b137d98a6" } } ], "extra": [ 1, 46, 92, 148, 241, 174, 50, 43, 220, 221, 190, 244, 149, 26, 250, 74, 54, 48, 163, 218, 173, 28, 146, 185, 15, 180, 202, 17, 6, 55, 211, 80, 242, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 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