Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e20473b7405d4a134cb93644f26615a46834e6229f4d7aa3725daa2e45e4a4f

Tx prefix hash: e191ea2e48fd48c75c4a7c7d30117efab4da3046e175731ad76543a29f088955
Tx public key: dfa1526c1ef425ab47d6fb79eff00391c6f3eb1160c514370d6b8d5dd343dbe1
Timestamp: 1702904665 Timestamp [UCT]: 2023-12-18 13:04:25 Age [y:d:h:m:s]: 01:180:14:53:45
Block: 915827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390166 RingCT/type: yes/0
Extra: 01dfa1526c1ef425ab47d6fb79eff00391c6f3eb1160c514370d6b8d5dd343dbe102110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26122a0ecd99dbda756804231de0a59c5b8efac6788e1b03a346ecf607671f9d 0.600000000000 1373261 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": 915837, "vin": [ { "gen": { "height": 915827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26122a0ecd99dbda756804231de0a59c5b8efac6788e1b03a346ecf607671f9d" } } ], "extra": [ 1, 223, 161, 82, 108, 30, 244, 37, 171, 71, 214, 251, 121, 239, 240, 3, 145, 198, 243, 235, 17, 96, 197, 20, 55, 13, 107, 141, 93, 211, 67, 219, 225, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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