Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc1d618466379fa2b6f2756894e610568aa13ecff2334f5847534549f21fccfb

Tx prefix hash: 6a6b622b8a4a9457b16be6fcbc1f0446dbf5db9759708e48c7f532c087dce1d9
Tx public key: 3a1e1a14b914aae8699bc3aa3bcbcc99a6c0d6975032a16a633ca77298486795
Timestamp: 1698151160 Timestamp [UCT]: 2023-10-24 12:39:20 Age [y:d:h:m:s]: 02:029:04:40:26
Block: 876630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540460 RingCT/type: yes/0
Extra: 013a1e1a14b914aae8699bc3aa3bcbcc99a6c0d6975032a16a633ca7729848679502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.764470834000 dcy

stealth address amount amount idx
00: 91e06ad217d6407616370b34b4d9b5776c32315117737c4e6fe8cf10047130be 0.764470834000 1331964 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": 876640, "vin": [ { "gen": { "height": 876630 } } ], "vout": [ { "amount": 764470834, "target": { "key": "91e06ad217d6407616370b34b4d9b5776c32315117737c4e6fe8cf10047130be" } } ], "extra": [ 1, 58, 30, 26, 20, 185, 20, 170, 232, 105, 155, 195, 170, 59, 203, 204, 153, 166, 192, 214, 151, 80, 50, 161, 106, 99, 60, 167, 114, 152, 72, 103, 149, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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