Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1de139b5d27b5e2de31e56197b0107868e67267a769374024b985c1d713b9cec

Tx prefix hash: c78e69aa0a1ca36e0f2092ba6f95f2740020b60f3f35fb82dfc2ea1f944bf92b
Tx public key: 347270232961379ff3495d1ff8b07de6e44144676d0f0f5c613b703b6bcbe325
Timestamp: 1715116017 Timestamp [UCT]: 2024-05-07 21:06:57 Age [y:d:h:m:s]: 00:136:16:34:20
Block: 1017068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97911 RingCT/type: yes/0
Extra: 01347270232961379ff3495d1ff8b07de6e44144676d0f0f5c613b703b6bcbe3250211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c107dd09bb4f696dccc80ac4c5d938656d4e9a2b009d4490ef85112c055c1b5a 0.600000000000 1480835 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": 1017078, "vin": [ { "gen": { "height": 1017068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c107dd09bb4f696dccc80ac4c5d938656d4e9a2b009d4490ef85112c055c1b5a" } } ], "extra": [ 1, 52, 114, 112, 35, 41, 97, 55, 159, 243, 73, 93, 31, 248, 176, 125, 230, 228, 65, 68, 103, 109, 15, 15, 92, 97, 59, 112, 59, 107, 203, 227, 37, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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