Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61bd16134d034ca9d1c91e00d2602ca37e4a377aca159ad5b02fa3969c52da95

Tx prefix hash: 954a4d9c3b17e91edc7a82c4c34368c8d71fc85cc0dcdd4544bd836f7df8ea8a
Tx public key: 433f1d9d3d6306baf6482743cf9ac2660fd2bfd8398f79806035c418742adb37
Timestamp: 1580263508 Timestamp [UCT]: 2020-01-29 02:05:08 Age [y:d:h:m:s]: 05:107:00:48:22
Block: 54292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228160 RingCT/type: yes/0
Extra: 01433f1d9d3d6306baf6482743cf9ac2660fd2bfd8398f79806035c418742adb37021100000002391a8d0e000000000000000000

1 output(s) for total of 405.610223552000 dcy

stealth address amount amount idx
00: a73d9a89d95ba6849b1f7da6c1371dad8f4291faa05f8254479402b8a1cec019 405.610223552000 100636 of 0

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": 54302, "vin": [ { "gen": { "height": 54292 } } ], "vout": [ { "amount": 405610223552, "target": { "key": "a73d9a89d95ba6849b1f7da6c1371dad8f4291faa05f8254479402b8a1cec019" } } ], "extra": [ 1, 67, 63, 29, 157, 61, 99, 6, 186, 246, 72, 39, 67, 207, 154, 194, 102, 15, 210, 191, 216, 57, 143, 121, 128, 96, 53, 196, 24, 116, 42, 219, 55, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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