Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a700e37d8a7e3ea7cffa883af4c0234b40f155ff3c7f9bb2a75884de6d1ec8c

Tx prefix hash: 1d5527a8706d2d913e7d9ddf360e24df723245e216890f24038bd6aec597f09d
Tx public key: 62232475117c86167fb0235121d91654c569c83d700aa7abc6ee9eaa8dd661f3
Timestamp: 1708164790 Timestamp [UCT]: 2024-02-17 10:13:10 Age [y:d:h:m:s]: 01:048:03:22:55
Block: 959433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295437 RingCT/type: yes/0
Extra: 0162232475117c86167fb0235121d91654c569c83d700aa7abc6ee9eaa8dd661f30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59ff39fc711f4e72648b2b0b686d4857cc1874bd7f6b40ae17d80eedcd3c4932 0.600000000000 1418968 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": 959443, "vin": [ { "gen": { "height": 959433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59ff39fc711f4e72648b2b0b686d4857cc1874bd7f6b40ae17d80eedcd3c4932" } } ], "extra": [ 1, 98, 35, 36, 117, 17, 124, 134, 22, 127, 176, 35, 81, 33, 217, 22, 84, 197, 105, 200, 61, 112, 10, 167, 171, 198, 238, 158, 170, 141, 214, 97, 243, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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