Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e576659093363c40168e2fb0e9ca6982298089cddb910b60ea0b9962276e09

Tx prefix hash: 7c28b670ed27f8014a8315ed62b0804528dab116bf25e687f3cb5d1ba5eafeba
Tx public key: 26f5aead9d971269e9989618b4e775f238a87453c953c97fd7e6953266f5d193
Timestamp: 1750500700 Timestamp [UCT]: 2025-06-21 10:11:40 Age [y:d:h:m:s]: 00:147:16:16:30
Block: 1309683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103396 RingCT/type: yes/0
Extra: 0126f5aead9d971269e9989618b4e775f238a87453c953c97fd7e6953266f5d193021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4b6742b93d6f8087c932f17ffec514c5ef7858f9363397f4b4d2524804f80a6 0.600000000000 1797300 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": 1309693, "vin": [ { "gen": { "height": 1309683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4b6742b93d6f8087c932f17ffec514c5ef7858f9363397f4b4d2524804f80a6" } } ], "extra": [ 1, 38, 245, 174, 173, 157, 151, 18, 105, 233, 152, 150, 24, 180, 231, 117, 242, 56, 168, 116, 83, 201, 83, 201, 127, 215, 230, 149, 50, 102, 245, 209, 147, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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