Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fcb03b672001985ecb6514cc11b7c3dfebd9874fd2f697977fd1c783c19662d

Tx prefix hash: 22c468420a2005e60c83fc16dfbc5f600c60a253fba22c580cb5836119a71375
Tx public key: 0a9a0fc073cbba151dcddd0ecc5d0deea26d56f46640f8915b2e1031fcfe5d1c
Timestamp: 1620993592 Timestamp [UCT]: 2021-05-14 11:59:52 Age [y:d:h:m:s]: 03:198:06:48:26
Block: 260479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 902545 RingCT/type: yes/0
Extra: 010a9a0fc073cbba151dcddd0ecc5d0deea26d56f46640f8915b2e1031fcfe5d1c021100000006a72c95e5000000000000000000

1 output(s) for total of 84.125080094000 dcy

stealth address amount amount idx
00: 39b3d43db359e693fbad5000c1aa28041245a253743209d18cfba9e4d3caea0a 84.125080094000 548566 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": 260489, "vin": [ { "gen": { "height": 260479 } } ], "vout": [ { "amount": 84125080094, "target": { "key": "39b3d43db359e693fbad5000c1aa28041245a253743209d18cfba9e4d3caea0a" } } ], "extra": [ 1, 10, 154, 15, 192, 115, 203, 186, 21, 29, 205, 221, 14, 204, 93, 13, 238, 162, 109, 86, 244, 102, 64, 248, 145, 91, 46, 16, 49, 252, 254, 93, 28, 2, 17, 0, 0, 0, 6, 167, 44, 149, 229, 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