Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77409b826723c6514d98644edf4c259d0bb4664327c798ea97b8d96f67731ee1

Tx prefix hash: 21766f5b129b421df12aa984a7cb52c480e5c4770db5bacf0defa142149b7bf7
Tx public key: cf01dd009bcccba4162e97fd893606bcf110fd295aa8e23dd5b4f6a55a8362e4
Timestamp: 1715114596 Timestamp [UCT]: 2024-05-07 20:43:16 Age [y:d:h:m:s]: 00:344:14:59:49
Block: 1017059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246338 RingCT/type: yes/0
Extra: 01cf01dd009bcccba4162e97fd893606bcf110fd295aa8e23dd5b4f6a55a8362e40211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcbac405a0af67765be8d190887d50824d2b14ab04513aff5c1768a7f8a4932b 0.600000000000 1480822 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": 1017069, "vin": [ { "gen": { "height": 1017059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcbac405a0af67765be8d190887d50824d2b14ab04513aff5c1768a7f8a4932b" } } ], "extra": [ 1, 207, 1, 221, 0, 155, 204, 203, 164, 22, 46, 151, 253, 137, 54, 6, 188, 241, 16, 253, 41, 90, 168, 226, 61, 213, 180, 246, 165, 90, 131, 98, 228, 2, 17, 0, 0, 0, 8, 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