Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa43ea835cb18ceb948b96687b9de0c2efb7b28b4a773476f711f78f7a8829a7

Tx prefix hash: 589cf640d3cf646c48e6911a98d344dab576f2366bf51219945dcf40bfe4756c
Tx public key: 106438c6eccef4de1a814b4efa811ee88beab69a2ebfca7b4c030b5a9c36cc3c
Timestamp: 1656434309 Timestamp [UCT]: 2022-06-28 16:38:29 Age [y:d:h:m:s]: 02:261:23:10:43
Block: 532308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 708340 RingCT/type: yes/0
Extra: 01106438c6eccef4de1a814b4efa811ee88beab69a2ebfca7b4c030b5a9c36cc3c02110000000ec9067537000000000000000000

1 output(s) for total of 10.574084646000 dcy

stealth address amount amount idx
00: 1718f8025fb9979d192ef22263eff274a0f269657ee25eea37949abc29aef529 10.574084646000 961537 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": 532318, "vin": [ { "gen": { "height": 532308 } } ], "vout": [ { "amount": 10574084646, "target": { "key": "1718f8025fb9979d192ef22263eff274a0f269657ee25eea37949abc29aef529" } } ], "extra": [ 1, 16, 100, 56, 198, 236, 206, 244, 222, 26, 129, 75, 78, 250, 129, 30, 232, 139, 234, 182, 154, 46, 191, 202, 123, 76, 3, 11, 90, 156, 54, 204, 60, 2, 17, 0, 0, 0, 14, 201, 6, 117, 55, 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