Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a957dc86ee1cdbe205f21ab7ebef55916a30add58aec3c2eb35f6ba279bd936

Tx prefix hash: abff91a47d758f2025eff65ffcd9f2b6a28e1f06d1ed803c8ad9767485681b72
Tx public key: 88e5fcfde003a0fbf2f1fba083df472c51c7a1d3e78adf3904efa5ab0051aaa8
Timestamp: 1659991562 Timestamp [UCT]: 2022-08-08 20:46:02 Age [y:d:h:m:s]: 02:230:17:54:04
Block: 561648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686091 RingCT/type: yes/0
Extra: 0188e5fcfde003a0fbf2f1fba083df472c51c7a1d3e78adf3904efa5ab0051aaa802110000000124ffc81c000000000000000000

1 output(s) for total of 8.453316702000 dcy

stealth address amount amount idx
00: e8d1c76aece06480b119c444d239c8e2c008f19ea712af96c8035158abeba86b 8.453316702000 994082 of 0

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": 561658, "vin": [ { "gen": { "height": 561648 } } ], "vout": [ { "amount": 8453316702, "target": { "key": "e8d1c76aece06480b119c444d239c8e2c008f19ea712af96c8035158abeba86b" } } ], "extra": [ 1, 136, 229, 252, 253, 224, 3, 160, 251, 242, 241, 251, 160, 131, 223, 71, 44, 81, 199, 161, 211, 231, 138, 223, 57, 4, 239, 165, 171, 0, 81, 170, 168, 2, 17, 0, 0, 0, 1, 36, 255, 200, 28, 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