Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 563fd17ed522da10fd4b9aff6adb19440726c08b6cfe270ddfafbb0d35f898c0

Tx prefix hash: afbd4e4fd2b9bf54b28ff75a9f8b775f63681e6df04729cc5ba45c6e79195e1a
Tx public key: e22e1d6bceeda897a25133bf1737f04b68d313350bd7cda3f683d21932f1d1b2
Timestamp: 1717022705 Timestamp [UCT]: 2024-05-29 22:45:05 Age [y:d:h:m:s]: 00:296:02:18:04
Block: 1032870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211618 RingCT/type: yes/0
Extra: 01e22e1d6bceeda897a25133bf1737f04b68d313350bd7cda3f683d21932f1d1b202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6af18e0ba8df4ef8dde2f0a2d9e31be77e56b07de850aabcac5c370848178fa 0.600000000000 1501325 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": 1032880, "vin": [ { "gen": { "height": 1032870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6af18e0ba8df4ef8dde2f0a2d9e31be77e56b07de850aabcac5c370848178fa" } } ], "extra": [ 1, 226, 46, 29, 107, 206, 237, 168, 151, 162, 81, 51, 191, 23, 55, 240, 75, 104, 211, 19, 53, 11, 215, 205, 163, 246, 131, 210, 25, 50, 241, 209, 178, 2, 17, 0, 0, 0, 1, 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