Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c840d8413290a4f11ffeb1db958df049814991b5d3ac14493de79741f4bc90cf

Tx prefix hash: 8c5cb5253312c53ca12f45b818eb524c8872676cc1fa93b6ff37bd0eee7dfde2
Tx public key: 368f22ee1b7bb25aa2fdfcfd95ffc9baa88b70ecfa1d554b94db71aa9db279f5
Timestamp: 1703612649 Timestamp [UCT]: 2023-12-26 17:44:09 Age [y:d:h:m:s]: 01:317:14:13:31
Block: 921692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485823 RingCT/type: yes/0
Extra: 01368f22ee1b7bb25aa2fdfcfd95ffc9baa88b70ecfa1d554b94db71aa9db279f502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67fb13d71958a70562b3bb337018ba829ce381e2c9c3b9a04d75cafba88fbb77 0.600000000000 1379384 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": 921702, "vin": [ { "gen": { "height": 921692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67fb13d71958a70562b3bb337018ba829ce381e2c9c3b9a04d75cafba88fbb77" } } ], "extra": [ 1, 54, 143, 34, 238, 27, 123, 178, 90, 162, 253, 252, 253, 149, 255, 201, 186, 168, 139, 112, 236, 250, 29, 85, 75, 148, 219, 113, 170, 157, 178, 121, 245, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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