Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63696dd3a14af7b4171ba0af876d043464f28cf61842fdfadeddf690fc025076

Tx prefix hash: 79ce533b25390ee7801450b37f72b72217b5e2b72f207ce41785b1c652d6c3fc
Tx public key: aa7d3be9d898178a757a2b31b939941c4f5d5a469d95b96e3f1024def9968bfb
Timestamp: 1696540351 Timestamp [UCT]: 2023-10-05 21:12:31 Age [y:d:h:m:s]: 01:180:01:15:07
Block: 863263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389720 RingCT/type: yes/0
Extra: 01aa7d3be9d898178a757a2b31b939941c4f5d5a469d95b96e3f1024def9968bfb02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.846547557000 dcy

stealth address amount amount idx
00: 504933d083c80367860994df347da726dc4a1e1581e01d97aa8cf4349be63b46 0.846547557000 1317713 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": 863273, "vin": [ { "gen": { "height": 863263 } } ], "vout": [ { "amount": 846547557, "target": { "key": "504933d083c80367860994df347da726dc4a1e1581e01d97aa8cf4349be63b46" } } ], "extra": [ 1, 170, 125, 59, 233, 216, 152, 23, 138, 117, 122, 43, 49, 185, 57, 148, 28, 79, 93, 90, 70, 157, 149, 185, 110, 63, 16, 36, 222, 249, 150, 139, 251, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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