Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 820c37dbb8f4f03e9e61960feb1921f91d41e0c4030ec0a19fbf15e2c37072a5

Tx prefix hash: abf151774f54835158dbe3c325428fbff4e66d17631c31fccdcc531fabf8a405
Tx public key: 0fa9da370295fe7debfa92371cbef54063d2f6d8c31437bb5f89e28a17c21e03
Timestamp: 1703610425 Timestamp [UCT]: 2023-12-26 17:07:05 Age [y:d:h:m:s]: 01:316:06:51:43
Block: 921681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484873 RingCT/type: yes/0
Extra: 010fa9da370295fe7debfa92371cbef54063d2f6d8c31437bb5f89e28a17c21e0302110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e9b6db82f71c31b1a1a84dc4cbb8fdbf14c6af0ba53be7c864bfab466db3fd2 0.600000000000 1379371 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": 921691, "vin": [ { "gen": { "height": 921681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e9b6db82f71c31b1a1a84dc4cbb8fdbf14c6af0ba53be7c864bfab466db3fd2" } } ], "extra": [ 1, 15, 169, 218, 55, 2, 149, 254, 125, 235, 250, 146, 55, 28, 190, 245, 64, 99, 210, 246, 216, 195, 20, 55, 187, 95, 137, 226, 138, 23, 194, 30, 3, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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