Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecedd39a6339c835f1ee5138ba52129f2516f8e6e123be448b15ce63c471f837

Tx prefix hash: 351520073b8cb3a7ae9a6463dbfd270b7a0e7168aee89b2517dd6cfba1c5b3e3
Tx public key: 76b7c90f751c7964f354ecf2cbb7b3ff54395724261c4df30ed8a52123f8215b
Timestamp: 1719350582 Timestamp [UCT]: 2024-06-25 21:23:02 Age [y:d:h:m:s]: 00:266:14:08:40
Block: 1052159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190513 RingCT/type: yes/0
Extra: 0176b7c90f751c7964f354ecf2cbb7b3ff54395724261c4df30ed8a52123f8215b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77532b72573d973241cb5de5d3bccd289fc80e5f2b81f202a3298846acbbeb56 0.600000000000 1522480 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": 1052169, "vin": [ { "gen": { "height": 1052159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77532b72573d973241cb5de5d3bccd289fc80e5f2b81f202a3298846acbbeb56" } } ], "extra": [ 1, 118, 183, 201, 15, 117, 28, 121, 100, 243, 84, 236, 242, 203, 183, 179, 255, 84, 57, 87, 36, 38, 28, 77, 243, 14, 216, 165, 33, 35, 248, 33, 91, 2, 17, 0, 0, 0, 1, 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