Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f57a6d84b3382f01840c65d324c28eded7c54339078dd54bdfb628a0afec06

Tx prefix hash: 391b73f0d0984eb02ae0f415abb91788604c970d8127580fea8a8b59a3d5feb0
Tx public key: 7f77662fd741f9c1f9aeca33c26e9579052549821870a3c4c49ce08ea198cb63
Timestamp: 1716258944 Timestamp [UCT]: 2024-05-21 02:35:44 Age [y:d:h:m:s]: 00:306:03:44:47
Block: 1026556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218806 RingCT/type: yes/0
Extra: 017f77662fd741f9c1f9aeca33c26e9579052549821870a3c4c49ce08ea198cb6302110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7f52488f5b38746336e18693def78d1cdd537fb23e97fb7432c653f5944054 0.600000000000 1493699 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": 1026566, "vin": [ { "gen": { "height": 1026556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7f52488f5b38746336e18693def78d1cdd537fb23e97fb7432c653f5944054" } } ], "extra": [ 1, 127, 119, 102, 47, 215, 65, 249, 193, 249, 174, 202, 51, 194, 110, 149, 121, 5, 37, 73, 130, 24, 112, 163, 196, 196, 156, 224, 142, 161, 152, 203, 99, 2, 17, 0, 0, 0, 11, 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