Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83f44e1ef52b2f05094ac7bbb4c2da3fb1b51d7612e83c6215e257ab9370a7b2

Tx prefix hash: 614c44ce0b5fa2bc44af1c0ddf595869046f9686a649e0077dc46e8b25cee474
Tx public key: 9bd056e3e3771101efdbf7f4ae559fc2da67630e65f4123c602838a2a1e3c077
Timestamp: 1713490516 Timestamp [UCT]: 2024-04-19 01:35:16 Age [y:d:h:m:s]: 00:294:02:30:29
Block: 1003581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210253 RingCT/type: yes/0
Extra: 019bd056e3e3771101efdbf7f4ae559fc2da67630e65f4123c602838a2a1e3c07702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f11fc026daef2eaf7d1ec7dd6866df1398e3a6359519125933ec1245d9274470 0.600000000000 1464123 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": 1003591, "vin": [ { "gen": { "height": 1003581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f11fc026daef2eaf7d1ec7dd6866df1398e3a6359519125933ec1245d9274470" } } ], "extra": [ 1, 155, 208, 86, 227, 227, 119, 17, 1, 239, 219, 247, 244, 174, 85, 159, 194, 218, 103, 99, 14, 101, 244, 18, 60, 96, 40, 56, 162, 161, 227, 192, 119, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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