Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cde17331e128a447431baa69d20213f93554b008cf451f717e5524fbbbe69a6

Tx prefix hash: af0b59d5b0dd1b367198f5d95a0f3aae2e8046bcfefb5a58c099d0dba010c766
Tx public key: 7593eec2f0ad8aa47cb65dcefbac7c541f89eb30c18270039d9ba89692922ff5
Timestamp: 1740904689 Timestamp [UCT]: 2025-03-02 08:38:09 Age [y:d:h:m:s]: 00:263:17:00:34
Block: 1230405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186213 RingCT/type: yes/0
Extra: 017593eec2f0ad8aa47cb65dcefbac7c541f89eb30c18270039d9ba89692922ff50211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73fb3f1e32d701b03626725e2ddf64e4035ae8405442af704fd6d0829e6df532 0.600000000000 1717302 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": 1230415, "vin": [ { "gen": { "height": 1230405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73fb3f1e32d701b03626725e2ddf64e4035ae8405442af704fd6d0829e6df532" } } ], "extra": [ 1, 117, 147, 238, 194, 240, 173, 138, 164, 124, 182, 93, 206, 251, 172, 124, 84, 31, 137, 235, 48, 193, 130, 112, 3, 157, 155, 168, 150, 146, 146, 47, 245, 2, 17, 0, 0, 0, 9, 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