Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e235a6d77ec7aefc93a341b7f3c0da3701395d3a0fb4c396b6eeab822c5ca77b

Tx prefix hash: 2384ac9acd1941535fb7f145e0cee2f84a7430b3b90c8072f38c23cb6f94c452
Tx public key: a66f3f91d57d9637414d04256e7338077be7574169fe798726c7058c1cbadf26
Timestamp: 1680960237 Timestamp [UCT]: 2023-04-08 13:23:57 Age [y:d:h:m:s]: 02:023:06:38:31
Block: 734230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538710 RingCT/type: yes/0
Extra: 01a66f3f91d57d9637414d04256e7338077be7574169fe798726c7058c1cbadf2602110000000175e3f0e9000000000000000000

1 output(s) for total of 2.265642813000 dcy

stealth address amount amount idx
00: da829869f9b65069633a22ea404a17b46cd8311fc74aaafcaa5624197dbc5d03 2.265642813000 1180401 of 0

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": 734240, "vin": [ { "gen": { "height": 734230 } } ], "vout": [ { "amount": 2265642813, "target": { "key": "da829869f9b65069633a22ea404a17b46cd8311fc74aaafcaa5624197dbc5d03" } } ], "extra": [ 1, 166, 111, 63, 145, 213, 125, 150, 55, 65, 77, 4, 37, 110, 115, 56, 7, 123, 231, 87, 65, 105, 254, 121, 135, 38, 199, 5, 140, 28, 186, 223, 38, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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