Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 041fefee8f4dc7eba0dcd4bfcf1a06a492d334b8dd6473588059ec166600b0fc

Tx prefix hash: cd70521e4cac5a048c15751a0279761ebcfdc4c6a9d01f6942891519cffed920
Tx public key: d26b90f10b37f8c314a5b75b02536d274d649b552ba60d857669c61e725b9b4c
Timestamp: 1715204495 Timestamp [UCT]: 2024-05-08 21:41:35 Age [y:d:h:m:s]: 01:197:02:40:25
Block: 1017812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399495 RingCT/type: yes/0
Extra: 01d26b90f10b37f8c314a5b75b02536d274d649b552ba60d857669c61e725b9b4c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8cbd3781dee34396b20166f0b352969ab90e8138533a54571c6da22e28a5fe7 0.600000000000 1481597 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": 1017822, "vin": [ { "gen": { "height": 1017812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8cbd3781dee34396b20166f0b352969ab90e8138533a54571c6da22e28a5fe7" } } ], "extra": [ 1, 210, 107, 144, 241, 11, 55, 248, 195, 20, 165, 183, 91, 2, 83, 109, 39, 77, 100, 155, 85, 43, 166, 13, 133, 118, 105, 198, 30, 114, 91, 155, 76, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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