Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 352fe17909a11bcd60c632e7eae7b30a7f02c417a5d7c50b7c6ff6b45ab54d17

Tx prefix hash: 4a7f99e68fdcd4f0838c7e3951276cb3ab13990533ca1b707623cf5354e48f6a
Tx public key: a96f84257cac8047e597e07de60ca91e095471e94367f1613381a70ce0cb67a3
Timestamp: 1693217965 Timestamp [UCT]: 2023-08-28 10:19:25 Age [y:d:h:m:s]: 02:078:04:09:03
Block: 835687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 575598 RingCT/type: yes/0
Extra: 01a96f84257cac8047e597e07de60ca91e095471e94367f1613381a70ce0cb67a30211000000024b8f5122000000000000000000

1 output(s) for total of 1.044773471000 dcy

stealth address amount amount idx
00: 7a40caa79fccb33fa4d60c315d64fdb9f66ad0d26e9745a08f347c9041023f47 1.044773471000 1288251 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": 835697, "vin": [ { "gen": { "height": 835687 } } ], "vout": [ { "amount": 1044773471, "target": { "key": "7a40caa79fccb33fa4d60c315d64fdb9f66ad0d26e9745a08f347c9041023f47" } } ], "extra": [ 1, 169, 111, 132, 37, 124, 172, 128, 71, 229, 151, 224, 125, 230, 12, 169, 30, 9, 84, 113, 233, 67, 103, 241, 97, 51, 129, 167, 12, 224, 203, 103, 163, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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