Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7167986975ca4e5716a6caf93603d14dcde761f9cd10c9f4528f7e1a79b3cc3e

Tx prefix hash: abf12ec930d12b34f18966d8c9e729451017da77b42185c4c4f23147f05077d7
Tx public key: 7b47737f0bf209a43ae4550e42577ec1647d0a964f90df1160d7addf57ddb5f1
Timestamp: 1702517966 Timestamp [UCT]: 2023-12-14 01:39:26 Age [y:d:h:m:s]: 01:139:03:14:11
Block: 912621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360579 RingCT/type: yes/0
Extra: 017b47737f0bf209a43ae4550e42577ec1647d0a964f90df1160d7addf57ddb5f1021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87bd8a56cf9edafe2deb72ab4128d4d5756072416f5fe716c15e601c8b6ebb55 0.600000000000 1369853 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": 912631, "vin": [ { "gen": { "height": 912621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87bd8a56cf9edafe2deb72ab4128d4d5756072416f5fe716c15e601c8b6ebb55" } } ], "extra": [ 1, 123, 71, 115, 127, 11, 242, 9, 164, 58, 228, 85, 14, 66, 87, 126, 193, 100, 125, 10, 150, 79, 144, 223, 17, 96, 215, 173, 223, 87, 221, 181, 241, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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