Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce87cda0c6da3e91486f5daa16ff23d606502f4edb800f3d80738c48bc5089e

Tx prefix hash: d4c97a4ab7cf9699f299232a137368e0cde6fea8fc368f07f952322d1496a8e2
Tx public key: bb921f6a8ef0a7d6409a17b719c46e516aafd2282534a52864495a337ef12e22
Timestamp: 1712918462 Timestamp [UCT]: 2024-04-12 10:41:02 Age [y:d:h:m:s]: 01:012:11:24:58
Block: 998826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269893 RingCT/type: yes/0
Extra: 01bb921f6a8ef0a7d6409a17b719c46e516aafd2282534a52864495a337ef12e2202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 173b9ab71698b7c8d8bf1717aa696113248a5e380d0fae7146aa1d8a8cf6fb58 0.600000000000 1459290 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": 998836, "vin": [ { "gen": { "height": 998826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "173b9ab71698b7c8d8bf1717aa696113248a5e380d0fae7146aa1d8a8cf6fb58" } } ], "extra": [ 1, 187, 146, 31, 106, 142, 240, 167, 214, 64, 154, 23, 183, 25, 196, 110, 81, 106, 175, 210, 40, 37, 52, 165, 40, 100, 73, 90, 51, 126, 241, 46, 34, 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