Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 609c24a9cea54e545cfa8411c2f902cb60573a4e474f6cb4831196d0eb413499

Tx prefix hash: 1be0f17a38d221aa99bad3b0ec4d16ab926faf483937c9deb4ef87e1e14d5ecb
Tx public key: 7f1bdc115104d38e744a2dae0cae63a550a7f3284594e40c32e4638302ca9fec
Timestamp: 1736277564 Timestamp [UCT]: 2025-01-07 19:19:24 Age [y:d:h:m:s]: 00:083:03:06:00
Block: 1192364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59193 RingCT/type: yes/0
Extra: 017f1bdc115104d38e744a2dae0cae63a550a7f3284594e40c32e4638302ca9fec021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 596c214b766ec6e4df2d04aac78f18bcb9143989d0c30f62a91c10c016e27e2f 0.600000000000 1678915 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": 1192374, "vin": [ { "gen": { "height": 1192364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "596c214b766ec6e4df2d04aac78f18bcb9143989d0c30f62a91c10c016e27e2f" } } ], "extra": [ 1, 127, 27, 220, 17, 81, 4, 211, 142, 116, 74, 45, 174, 12, 174, 99, 165, 80, 167, 243, 40, 69, 148, 228, 12, 50, 228, 99, 131, 2, 202, 159, 236, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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