Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40039bd38de678f6a6ea509dc594317c779b20bfce3e5a9df83f74edb53ca042

Tx prefix hash: 58735db749f42163404834803a845c3cc8c9ba786c2504d26275e69a979bd745
Tx public key: ec7f6f3118dbbe074a24c7e466510cbc8df255ba52f769f1b8ff461bee8a9fb4
Timestamp: 1734464320 Timestamp [UCT]: 2024-12-17 19:38:40 Age [y:d:h:m:s]: 00:129:00:04:34
Block: 1177381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91986 RingCT/type: yes/0
Extra: 01ec7f6f3118dbbe074a24c7e466510cbc8df255ba52f769f1b8ff461bee8a9fb40211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fd088828a38a6b1945f896d5101961a337dfdf974137039d3d62ee01da6a1dc 0.600000000000 1663752 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": 1177391, "vin": [ { "gen": { "height": 1177381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fd088828a38a6b1945f896d5101961a337dfdf974137039d3d62ee01da6a1dc" } } ], "extra": [ 1, 236, 127, 111, 49, 24, 219, 190, 7, 74, 36, 199, 228, 102, 81, 12, 188, 141, 242, 85, 186, 82, 247, 105, 241, 184, 255, 70, 27, 238, 138, 159, 180, 2, 17, 0, 0, 0, 2, 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