Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5e9d8f60fb24623dbac6f83c3bcf9029538b89ff250b1cf40e5b5d4c551488c

Tx prefix hash: 750c1116381372468801c2abf07c9c44a536acee4c119e441128f41a67bf50a9
Tx public key: c611d7e0a411c4b37924e9012a62739bd5ebc372272f53793fdf2f068c88f992
Timestamp: 1722123351 Timestamp [UCT]: 2024-07-27 23:35:51 Age [y:d:h:m:s]: 00:250:09:44:28
Block: 1075158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178874 RingCT/type: yes/0
Extra: 01c611d7e0a411c4b37924e9012a62739bd5ebc372272f53793fdf2f068c88f99202110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78fe41d0af81cf2938d8bc577e0f08aa576064eff93f39844d1a8e284f9fda6c 0.600000000000 1547681 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": 1075168, "vin": [ { "gen": { "height": 1075158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78fe41d0af81cf2938d8bc577e0f08aa576064eff93f39844d1a8e284f9fda6c" } } ], "extra": [ 1, 198, 17, 215, 224, 164, 17, 196, 179, 121, 36, 233, 1, 42, 98, 115, 155, 213, 235, 195, 114, 39, 47, 83, 121, 63, 223, 47, 6, 140, 136, 249, 146, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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