Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864eda99f5c5b9da2ba2a833fc71ad6518cd90c1391b5e3335fe89f339e8db0f

Tx prefix hash: a44368ff8c61f83692ef9ea19e67e957bd994e4bdf1dc6cddb40b35ea54fdbaa
Tx public key: e5a1772fc27f270a7f9a9d41566f4b77d3f75783eced750c036056c0499b237b
Timestamp: 1711533726 Timestamp [UCT]: 2024-03-27 10:02:06 Age [y:d:h:m:s]: 01:063:16:16:44
Block: 987395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306494 RingCT/type: yes/0
Extra: 01e5a1772fc27f270a7f9a9d41566f4b77d3f75783eced750c036056c0499b237b02110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4bde08f03ace5bed8607ba82562f76c2422681e97eb8335e803664bf44ca097 0.600000000000 1447644 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": 987405, "vin": [ { "gen": { "height": 987395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4bde08f03ace5bed8607ba82562f76c2422681e97eb8335e803664bf44ca097" } } ], "extra": [ 1, 229, 161, 119, 47, 194, 127, 39, 10, 127, 154, 157, 65, 86, 111, 75, 119, 211, 247, 87, 131, 236, 237, 117, 12, 3, 96, 86, 192, 73, 155, 35, 123, 2, 17, 0, 0, 0, 19, 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