Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 686fbed4616f119e207c9390508ef98e71a0a6dfa9ae145e23efbc73c21c02bd

Tx prefix hash: 8ded83b0488f23b5866912b47012d84c7c6890d331b66cb883298e1f8339b499
Tx public key: 17cfb0967340f0d135f62cb9ee2b468373dd4d8749adcf04c9397a9d6d3f91d1
Timestamp: 1715355498 Timestamp [UCT]: 2024-05-10 15:38:18 Age [y:d:h:m:s]: 00:290:19:34:19
Block: 1019047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207849 RingCT/type: yes/0
Extra: 0117cfb0967340f0d135f62cb9ee2b468373dd4d8749adcf04c9397a9d6d3f91d102110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa7a9d65bb839fce02da9805356214fb370dc90d79f69a16faf3c4680f435b35 0.600000000000 1482912 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": 1019057, "vin": [ { "gen": { "height": 1019047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa7a9d65bb839fce02da9805356214fb370dc90d79f69a16faf3c4680f435b35" } } ], "extra": [ 1, 23, 207, 176, 150, 115, 64, 240, 209, 53, 246, 44, 185, 238, 43, 70, 131, 115, 221, 77, 135, 73, 173, 207, 4, 201, 57, 122, 157, 109, 63, 145, 209, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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