Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0a82b4a5f9cce68dc52097469e84c7c0c8f42c8b1b119689415445840db5d9

Tx prefix hash: 052a89ba9007944a6617a8d34262c46f3209d9975280baa5403b40db60ecc4bb
Tx public key: 8f20e10a9af4f8c3716c94c8c59e79fb0e59ca29731f482a2726ef2056931b8e
Timestamp: 1717526858 Timestamp [UCT]: 2024-06-04 18:47:38 Age [y:d:h:m:s]: 01:156:21:34:24
Block: 1037064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370700 RingCT/type: yes/0
Extra: 018f20e10a9af4f8c3716c94c8c59e79fb0e59ca29731f482a2726ef2056931b8e0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d6ff0cdb2498b1926a489fb74c3a731197a0b26627d231efa66efbcd3deb2a0 0.600000000000 1505595 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": 1037074, "vin": [ { "gen": { "height": 1037064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d6ff0cdb2498b1926a489fb74c3a731197a0b26627d231efa66efbcd3deb2a0" } } ], "extra": [ 1, 143, 32, 225, 10, 154, 244, 248, 195, 113, 108, 148, 200, 197, 158, 121, 251, 14, 89, 202, 41, 115, 31, 72, 42, 39, 38, 239, 32, 86, 147, 27, 142, 2, 17, 0, 0, 0, 6, 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