Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65d64f1061044861868f8d3fe79c6ed4ea0a8c3b5c88689858cd7179b67915bc

Tx prefix hash: 57263b07622751a8bae43f337663466e66e4f753b776d7ffb251cde2a4a2decc
Tx public key: 5b087650ad3dd34f91ca6603648a3d0f4f19131596c5cc20a64846ae1cadff64
Timestamp: 1701634876 Timestamp [UCT]: 2023-12-03 20:21:16 Age [y:d:h:m:s]: 01:144:11:46:52
Block: 905291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364442 RingCT/type: yes/0
Extra: 015b087650ad3dd34f91ca6603648a3d0f4f19131596c5cc20a64846ae1cadff64021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.614320614000 dcy

stealth address amount amount idx
00: d94d4fee946f38a63fdb722d12e0aea303f1273e756724bf4ed814954180a076 0.614320614000 1362172 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": 905301, "vin": [ { "gen": { "height": 905291 } } ], "vout": [ { "amount": 614320614, "target": { "key": "d94d4fee946f38a63fdb722d12e0aea303f1273e756724bf4ed814954180a076" } } ], "extra": [ 1, 91, 8, 118, 80, 173, 61, 211, 79, 145, 202, 102, 3, 100, 138, 61, 15, 79, 25, 19, 21, 150, 197, 204, 32, 166, 72, 70, 174, 28, 173, 255, 100, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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