Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef61019861e35a5291b9a567bc8bf6f99554b8479631eeb76c2148a1d73acd09

Tx prefix hash: 119327f74214c3fba3550d702fc7d2aa61cff28f34f2ee3804bd12a9e40eba4d
Tx public key: 469d80239e44d043a48c837c6e3f1fd78bfe580fb08991eca8236ba3e478b035
Timestamp: 1708678665 Timestamp [UCT]: 2024-02-23 08:57:45 Age [y:d:h:m:s]: 01:260:07:36:12
Block: 963696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444796 RingCT/type: yes/0
Extra: 01469d80239e44d043a48c837c6e3f1fd78bfe580fb08991eca8236ba3e478b0350211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0701489daf1f7be05b7037934461c2316a9f223f3f0c6bbe1233aa52730bff3c 0.600000000000 1423415 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": 963706, "vin": [ { "gen": { "height": 963696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0701489daf1f7be05b7037934461c2316a9f223f3f0c6bbe1233aa52730bff3c" } } ], "extra": [ 1, 70, 157, 128, 35, 158, 68, 208, 67, 164, 140, 131, 124, 110, 63, 31, 215, 139, 254, 88, 15, 176, 137, 145, 236, 168, 35, 107, 163, 228, 120, 176, 53, 2, 17, 0, 0, 0, 2, 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