Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 575da2e62a4344b39cb5dccfb4d204644f11d2fd2c08846bbd6dcb6ec26a4d37

Tx prefix hash: f6051ea9d4a945143640ef318ed52d3166fbe324fc21a1fe7a4cffa822c1f173
Tx public key: d662174619b310c75c91a09c97e2e489dfcd76d2347f5a3d35486685af6e336c
Timestamp: 1713376099 Timestamp [UCT]: 2024-04-17 17:48:19 Age [y:d:h:m:s]: 00:357:16:55:21
Block: 1002633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255729 RingCT/type: yes/0
Extra: 01d662174619b310c75c91a09c97e2e489dfcd76d2347f5a3d35486685af6e336c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1de6c793edb1c161686110c273816521e4aa0e4bfa9bb6948028392aad6cf73 0.600000000000 1463151 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": 1002643, "vin": [ { "gen": { "height": 1002633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1de6c793edb1c161686110c273816521e4aa0e4bfa9bb6948028392aad6cf73" } } ], "extra": [ 1, 214, 98, 23, 70, 25, 179, 16, 199, 92, 145, 160, 156, 151, 226, 228, 137, 223, 205, 118, 210, 52, 127, 90, 61, 53, 72, 102, 133, 175, 110, 51, 108, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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