Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b307234c90a5659c7b8c484e3f734ff47ef6d0d92add65b3f6c2f5bbf25b006

Tx prefix hash: f51605dd9c5a09f05b78503a475ae01661977bca87e077342490abc9d51b1691
Tx public key: 28328a1dbaeb29a24f61b65b26623b2426d23a22df3bea8644ea1fe0753511fc
Timestamp: 1703219916 Timestamp [UCT]: 2023-12-22 04:38:36 Age [y:d:h:m:s]: 01:095:00:36:32
Block: 918436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329021 RingCT/type: yes/0
Extra: 0128328a1dbaeb29a24f61b65b26623b2426d23a22df3bea8644ea1fe0753511fc0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fe3da66663f9106e71a4b05b8caedf9fda80674451953b9a4f59ad434d9a646 0.600000000000 1376080 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": 918446, "vin": [ { "gen": { "height": 918436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fe3da66663f9106e71a4b05b8caedf9fda80674451953b9a4f59ad434d9a646" } } ], "extra": [ 1, 40, 50, 138, 29, 186, 235, 41, 162, 79, 97, 182, 91, 38, 98, 59, 36, 38, 210, 58, 34, 223, 59, 234, 134, 68, 234, 31, 224, 117, 53, 17, 252, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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