Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0650a260c4877d38f219800661131a198f1fb1e94ad160f1043ac9bd6573e1

Tx prefix hash: 193f6636f16f2bc04b72fe6c40db045d2edb3ada41fd7b2bfeac664d96c4cdf8
Tx public key: 212b5e974ba16ce9e79f70624d204d76fc32dd3ffb72d598c8dacdc7d20fd224
Timestamp: 1732032294 Timestamp [UCT]: 2024-11-19 16:04:54 Age [y:d:h:m:s]: 00:004:18:30:16
Block: 1157222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3404 RingCT/type: yes/0
Extra: 01212b5e974ba16ce9e79f70624d204d76fc32dd3ffb72d598c8dacdc7d20fd224021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c018c3118a49e15eab6a2a94c839ba5726c6c659f6d8b22b8425516e3c7cafe8 0.600000000000 1642845 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": 1157232, "vin": [ { "gen": { "height": 1157222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c018c3118a49e15eab6a2a94c839ba5726c6c659f6d8b22b8425516e3c7cafe8" } } ], "extra": [ 1, 33, 43, 94, 151, 75, 161, 108, 233, 231, 159, 112, 98, 77, 32, 77, 118, 252, 50, 221, 63, 251, 114, 213, 152, 200, 218, 205, 199, 210, 15, 210, 36, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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