Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45df81c535c3ed6eeb6ce222d70caf5592618e20e21951be90879050047c549e

Tx prefix hash: 36f587bf3da0436d5ba4687bc1ecfc699b1295449d92a3e2c548dc71b95174a0
Tx public key: 8d0a3f4b4f8efff1b1daf648f87fd9cedf179141f05c15d0fbe56865dae773d2
Timestamp: 1699645860 Timestamp [UCT]: 2023-11-10 19:51:00 Age [y:d:h:m:s]: 02:000:05:04:51
Block: 888816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519921 RingCT/type: yes/0
Extra: 018d0a3f4b4f8efff1b1daf648f87fd9cedf179141f05c15d0fbe56865dae773d202110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.696600251000 dcy

stealth address amount amount idx
00: 4b0296d13f45a3df4377f445d9f5b283cec44c0b6cd5b5074af16fb2ffa27f30 0.696600251000 1344775 of 0

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": 888826, "vin": [ { "gen": { "height": 888816 } } ], "vout": [ { "amount": 696600251, "target": { "key": "4b0296d13f45a3df4377f445d9f5b283cec44c0b6cd5b5074af16fb2ffa27f30" } } ], "extra": [ 1, 141, 10, 63, 75, 79, 142, 255, 241, 177, 218, 246, 72, 248, 127, 217, 206, 223, 23, 145, 65, 240, 92, 21, 208, 251, 229, 104, 101, 218, 231, 115, 210, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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