Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c7603268c7ec0ea213fe60bb9bca5f7b22c111aea30e884cce3c3cf8176ce7

Tx prefix hash: f859fb51089d8cfc981c67e39c944bcffa97e113e4254a4c4fd1ec2c951086f1
Tx public key: 8f2d33b5aace47ff8d857bc089c0e07a2cd954fa1274f954b19c95790469c6ad
Timestamp: 1675371891 Timestamp [UCT]: 2023-02-02 21:04:51 Age [y:d:h:m:s]: 02:025:17:47:55
Block: 688444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539990 RingCT/type: yes/0
Extra: 018f2d33b5aace47ff8d857bc089c0e07a2cd954fa1274f954b19c95790469c6ad0211000000015029cbac000000000000000000

1 output(s) for total of 3.212914522000 dcy

stealth address amount amount idx
00: 0480a447878290d4adfaa2d5bb063fc1a7bb0ece9458b3187576c15ce3bb7321 3.212914522000 1131066 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": 688454, "vin": [ { "gen": { "height": 688444 } } ], "vout": [ { "amount": 3212914522, "target": { "key": "0480a447878290d4adfaa2d5bb063fc1a7bb0ece9458b3187576c15ce3bb7321" } } ], "extra": [ 1, 143, 45, 51, 181, 170, 206, 71, 255, 141, 133, 123, 192, 137, 192, 224, 122, 44, 217, 84, 250, 18, 116, 249, 84, 177, 156, 149, 121, 4, 105, 198, 173, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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