Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39da0001aa54b6f4da6959598995239cdb408e48a21649550993ad583cf5135d

Tx prefix hash: bafd9ce2c9957ba50486b91fa66c3fdd441090024b06745b184b50e6da1402f8
Tx public key: 3a263f6d2fa9cde90f9ffc6d7c298a94e196167837724a064ea5c9d6e48f86db
Timestamp: 1715509488 Timestamp [UCT]: 2024-05-12 10:24:48 Age [y:d:h:m:s]: 00:331:00:01:20
Block: 1020357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236558 RingCT/type: yes/0
Extra: 013a263f6d2fa9cde90f9ffc6d7c298a94e196167837724a064ea5c9d6e48f86db021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 019500bf5fc29f0e882d28c306cad8e67cd79c0b97e63b386ca3698a371ee6b4 0.600000000000 1484420 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": 1020367, "vin": [ { "gen": { "height": 1020357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "019500bf5fc29f0e882d28c306cad8e67cd79c0b97e63b386ca3698a371ee6b4" } } ], "extra": [ 1, 58, 38, 63, 109, 47, 169, 205, 233, 15, 159, 252, 109, 124, 41, 138, 148, 225, 150, 22, 120, 55, 114, 74, 6, 78, 165, 201, 214, 228, 143, 134, 219, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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