Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdfaedbf89a90a6ecf374826e077dbbda5e1ceb11a672ac86abd1a389b523db0

Tx prefix hash: 3cf8ccdf0027ac1be6a5f1a86a61b45c171663161d9fde151392f9104e066c80
Tx public key: eb682c0da377a8fb414bf9f3dd594ec419d6d7fd757dc2c8cc8171b87e8cbcc7
Timestamp: 1707857777 Timestamp [UCT]: 2024-02-13 20:56:17 Age [y:d:h:m:s]: 01:237:15:49:35
Block: 956890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428558 RingCT/type: yes/0
Extra: 01eb682c0da377a8fb414bf9f3dd594ec419d6d7fd757dc2c8cc8171b87e8cbcc70211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b54b4fd875fd01a97d8781498d092fe67f7d8c42ae046cefb1a02f3599231ea 0.600000000000 1416202 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": 956900, "vin": [ { "gen": { "height": 956890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b54b4fd875fd01a97d8781498d092fe67f7d8c42ae046cefb1a02f3599231ea" } } ], "extra": [ 1, 235, 104, 44, 13, 163, 119, 168, 251, 65, 75, 249, 243, 221, 89, 78, 196, 25, 214, 215, 253, 117, 125, 194, 200, 204, 129, 113, 184, 126, 140, 188, 199, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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