Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ef2c36333e660d53afd3a23000a25a38ddc2d425881e012d9422c7502cdb3a1

Tx prefix hash: 2f820774d0667a117fac43ac262dbb8117279182dc5d35e09b310dc52ab64161
Tx public key: 20b8d7c5bee68a4c40bf3c926eab42d93da02768e5b4f2a37a5519917c3e2343
Timestamp: 1710439231 Timestamp [UCT]: 2024-03-14 18:00:31 Age [y:d:h:m:s]: 00:346:04:05:20
Block: 978309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247478 RingCT/type: yes/0
Extra: 0120b8d7c5bee68a4c40bf3c926eab42d93da02768e5b4f2a37a5519917c3e23430211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08c9b35933c8594a6c56833243f9410fcecad70b37979705e82bbd529e237a55 0.600000000000 1438332 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": 978319, "vin": [ { "gen": { "height": 978309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08c9b35933c8594a6c56833243f9410fcecad70b37979705e82bbd529e237a55" } } ], "extra": [ 1, 32, 184, 215, 197, 190, 230, 138, 76, 64, 191, 60, 146, 110, 171, 66, 217, 61, 160, 39, 104, 229, 180, 242, 163, 122, 85, 25, 145, 124, 62, 35, 67, 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