Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96bb4d9e37686a13dd04f029eb6e88fb7e23114fb1a93f661e1484e942ebc382

Tx prefix hash: 2ed1742419fab54be5dda2ee9e2e37b69935d339b377a6eda1f83364f91013be
Tx public key: ad644b780d926b9fa7f6cb638c02b11873862d7b3f8ecf265b40d16e456b6a40
Timestamp: 1714679679 Timestamp [UCT]: 2024-05-02 19:54:39 Age [y:d:h:m:s]: 01:044:01:45:22
Block: 1013453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292352 RingCT/type: yes/0
Extra: 01ad644b780d926b9fa7f6cb638c02b11873862d7b3f8ecf265b40d16e456b6a400211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aa661e2e8c1dee52ea889a3dc70aec4f30abd76695bb349d40cf1bede2dfa41 0.600000000000 1476272 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": 1013463, "vin": [ { "gen": { "height": 1013453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aa661e2e8c1dee52ea889a3dc70aec4f30abd76695bb349d40cf1bede2dfa41" } } ], "extra": [ 1, 173, 100, 75, 120, 13, 146, 107, 159, 167, 246, 203, 99, 140, 2, 177, 24, 115, 134, 45, 123, 63, 142, 207, 38, 91, 64, 209, 110, 69, 107, 106, 64, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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