Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 617101cb53c4b458b61092b9c0595de1dd2116726824d286c0ae4d8902ae2591

Tx prefix hash: 9ca4c4fb943840a01d9c96d3d124fc46f1dbe15efb978276842a9364955be886
Tx public key: 50100d472c1042f2c43babc96f20e5f761737b7f7fc1c9e4b42b2846d9906005
Timestamp: 1702921307 Timestamp [UCT]: 2023-12-18 17:41:47 Age [y:d:h:m:s]: 01:069:21:59:48
Block: 915962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311066 RingCT/type: yes/0
Extra: 0150100d472c1042f2c43babc96f20e5f761737b7f7fc1c9e4b42b2846d990600502110000000975e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69991aac4cd1abc00fa7a3306ff6811260a4de3ad26704a994100fe83b20a472 0.600000000000 1373396 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": 915972, "vin": [ { "gen": { "height": 915962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69991aac4cd1abc00fa7a3306ff6811260a4de3ad26704a994100fe83b20a472" } } ], "extra": [ 1, 80, 16, 13, 71, 44, 16, 66, 242, 196, 59, 171, 201, 111, 32, 229, 247, 97, 115, 123, 127, 127, 193, 201, 228, 180, 43, 40, 70, 217, 144, 96, 5, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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