Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c16045ac0ab6768a05751eb383ac749fd340687181a7b0e11c514bc92e959372

Tx prefix hash: 98a1c2751b6e58647d42ffec17a8cf767b89c39de92c4d57978bc3c21388a15d
Tx public key: 77e348b6f408507f9177b5a029e3438b61a3d3f4a7b7a4f39c28e0879dba852a
Timestamp: 1730114191 Timestamp [UCT]: 2024-10-28 11:16:31 Age [y:d:h:m:s]: 00:137:12:04:38
Block: 1141335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98109 RingCT/type: yes/0
Extra: 0177e348b6f408507f9177b5a029e3438b61a3d3f4a7b7a4f39c28e0879dba852a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e164ec744d3e12992d12dd89eb5040593ed33276ee33a4c72b231f814bfb6b2d 0.600000000000 1625142 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": 1141345, "vin": [ { "gen": { "height": 1141335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e164ec744d3e12992d12dd89eb5040593ed33276ee33a4c72b231f814bfb6b2d" } } ], "extra": [ 1, 119, 227, 72, 182, 244, 8, 80, 127, 145, 119, 181, 160, 41, 227, 67, 139, 97, 163, 211, 244, 167, 183, 164, 243, 156, 40, 224, 135, 157, 186, 133, 42, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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