Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f1bce4fad5e9ffb807dd37601352e24e2e27a7ed3502de960db972ccb1a0aa

Tx prefix hash: 64f4c6ac5d85401a535691d28199c5099ac13700fc3a0e60e2a6f063def7e1cd
Tx public key: e8cd5e4766c94d031aa3b24256512114a8571edba9c506d8b4a2aaee8ae8a4e0
Timestamp: 1715047167 Timestamp [UCT]: 2024-05-07 01:59:27 Age [y:d:h:m:s]: 00:296:21:30:59
Block: 1016505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212182 RingCT/type: yes/0
Extra: 01e8cd5e4766c94d031aa3b24256512114a8571edba9c506d8b4a2aaee8ae8a4e00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6039357e3099e7468741947fa567a67a70404fcd5723a59253b0bc1b5373c972 0.600000000000 1480106 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": 1016515, "vin": [ { "gen": { "height": 1016505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6039357e3099e7468741947fa567a67a70404fcd5723a59253b0bc1b5373c972" } } ], "extra": [ 1, 232, 205, 94, 71, 102, 201, 77, 3, 26, 163, 178, 66, 86, 81, 33, 20, 168, 87, 30, 219, 169, 197, 6, 216, 180, 162, 170, 238, 138, 232, 164, 224, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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