Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae0bb7a27a5363f7ce8cef8407653f87defa1b2aec52cc2c02607bfbc4f49c06

Tx prefix hash: a54bf2dd253f3e666b2c604fc364add9a7e41cfa826bd44d3d3d5fe8f00d4cef
Tx public key: a6af671e79bfb3c1c2e816ef12088909ecdd7e120533a897ec8803f9f76a78de
Timestamp: 1719499965 Timestamp [UCT]: 2024-06-27 14:52:45 Age [y:d:h:m:s]: 00:306:16:24:49
Block: 1053405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219174 RingCT/type: yes/0
Extra: 01a6af671e79bfb3c1c2e816ef12088909ecdd7e120533a897ec8803f9f76a78de0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8870642a533be97ed04734327cbfa099ccf880d01f39383628c7f17a1e5015a 0.600000000000 1523752 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": 1053415, "vin": [ { "gen": { "height": 1053405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8870642a533be97ed04734327cbfa099ccf880d01f39383628c7f17a1e5015a" } } ], "extra": [ 1, 166, 175, 103, 30, 121, 191, 179, 193, 194, 232, 22, 239, 18, 8, 137, 9, 236, 221, 126, 18, 5, 51, 168, 151, 236, 136, 3, 249, 247, 106, 120, 222, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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