Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9794f1fee63c542f8ef4e7b09c4a8d28745bbe0166f33b318ddb97088ac2aa4

Tx prefix hash: 77a39bbfd2608a408d7b84d3d15514843a8d9011ea7308545bd9a107183a0c9e
Tx public key: 1090981926126e50b9f3645640df7748e88318416a8fdd555782e61bbd363123
Timestamp: 1712862283 Timestamp [UCT]: 2024-04-11 19:04:43 Age [y:d:h:m:s]: 00:359:05:43:51
Block: 998356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256844 RingCT/type: yes/0
Extra: 011090981926126e50b9f3645640df7748e88318416a8fdd555782e61bbd3631230211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6aa174becf88e2c3dfff50352127d6ff619b5c5e0c71ead88c0e697954aa968f 0.600000000000 1458802 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": 998366, "vin": [ { "gen": { "height": 998356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6aa174becf88e2c3dfff50352127d6ff619b5c5e0c71ead88c0e697954aa968f" } } ], "extra": [ 1, 16, 144, 152, 25, 38, 18, 110, 80, 185, 243, 100, 86, 64, 223, 119, 72, 232, 131, 24, 65, 106, 143, 221, 85, 87, 130, 230, 27, 189, 54, 49, 35, 2, 17, 0, 0, 0, 3, 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