Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6566d333fb83fd9d29f789835b11e184eb775af51c27cb6c4d7ea7ff2f19ba34

Tx prefix hash: 05f3ca11239024f625aa5b89fcca73f0797eaf90b0c2127336b7de0ebd4aea5b
Tx public key: d8bb0c755f147ecce93071911a9a9916a42d100c8ecab0e4deb22ca4c6bde026
Timestamp: 1713072689 Timestamp [UCT]: 2024-04-14 05:31:29 Age [y:d:h:m:s]: 00:355:01:41:44
Block: 1000106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253864 RingCT/type: yes/0
Extra: 01d8bb0c755f147ecce93071911a9a9916a42d100c8ecab0e4deb22ca4c6bde02602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bf6e468641fa5c6360e49f020588d218fc0bdf7f297e1db38aa41c4d1277194 0.600000000000 1460596 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": 1000116, "vin": [ { "gen": { "height": 1000106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bf6e468641fa5c6360e49f020588d218fc0bdf7f297e1db38aa41c4d1277194" } } ], "extra": [ 1, 216, 187, 12, 117, 95, 20, 126, 204, 233, 48, 113, 145, 26, 154, 153, 22, 164, 45, 16, 12, 142, 202, 176, 228, 222, 178, 44, 164, 198, 189, 224, 38, 2, 17, 0, 0, 0, 2, 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