Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6754b8f1a6e23747a463dad4e87f71db82a9b2133dc54206429f75fcc22e836

Tx prefix hash: 18e7fbaef2ce2a9906476b6984bc1b91365eede6605fa3583eb2087d35cf169a
Tx public key: baab15f58ae06e394a86cfa5e8fc48743f8ce596e03db4d6a32f035978c910b1
Timestamp: 1592761439 Timestamp [UCT]: 2020-06-21 17:43:59 Age [y:d:h:m:s]: 04:190:08:13:42
Block: 110231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074457 RingCT/type: yes/0
Extra: 01baab15f58ae06e394a86cfa5e8fc48743f8ce596e03db4d6a32f035978c910b102110000005346a11e8a000000000000000000

1 output(s) for total of 264.703501164000 dcy

stealth address amount amount idx
00: 3ba50f4783ccf4758296e7d35b5990f1a55786041afff214504d1ef0d9d86e81 264.703501164000 190871 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": 110241, "vin": [ { "gen": { "height": 110231 } } ], "vout": [ { "amount": 264703501164, "target": { "key": "3ba50f4783ccf4758296e7d35b5990f1a55786041afff214504d1ef0d9d86e81" } } ], "extra": [ 1, 186, 171, 21, 245, 138, 224, 110, 57, 74, 134, 207, 165, 232, 252, 72, 116, 63, 140, 229, 150, 224, 61, 180, 214, 163, 47, 3, 89, 120, 201, 16, 177, 2, 17, 0, 0, 0, 83, 70, 161, 30, 138, 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