Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49640e47813471c821be5a8af5d9a852eb9120cc3f6da01daec40733fc6bd5ba

Tx prefix hash: cc5ce35fc24b8edfcc0c0729a5130644096dd534d680031a81f571b40c6fab31
Tx public key: 17e7403354fd5c417fec17bbd3dd43f5cb06891d6787ee1213c29afd8d6c9a88
Timestamp: 1720329751 Timestamp [UCT]: 2024-07-07 05:22:31 Age [y:d:h:m:s]: 00:268:12:05:35
Block: 1060288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191823 RingCT/type: yes/0
Extra: 0117e7403354fd5c417fec17bbd3dd43f5cb06891d6787ee1213c29afd8d6c9a8802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b17050e279176a578be6a5a39fde9cf5be1f82f953a6be7a1eef45037e82b1b 0.600000000000 1530759 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": 1060298, "vin": [ { "gen": { "height": 1060288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b17050e279176a578be6a5a39fde9cf5be1f82f953a6be7a1eef45037e82b1b" } } ], "extra": [ 1, 23, 231, 64, 51, 84, 253, 92, 65, 127, 236, 23, 187, 211, 221, 67, 245, 203, 6, 137, 29, 103, 135, 238, 18, 19, 194, 154, 253, 141, 108, 154, 136, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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