Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3111a97c62089680b87e1ba8b707e3313b8ed517eefa409cb8d006c80bf2bef

Tx prefix hash: 364fa7205c06ea655b080d31da59d365f132aa03c63b75be08ecdb4128a31820
Tx public key: 7e7c26ee7d9440c2f4bdf259a4e927482f443f9122574cf1d6b39ce454ef57e1
Timestamp: 1583633785 Timestamp [UCT]: 2020-03-08 02:16:25 Age [y:d:h:m:s]: 04:294:15:21:58
Block: 78345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105386 RingCT/type: yes/0
Extra: 017e7c26ee7d9440c2f4bdf259a4e927482f443f9122574cf1d6b39ce454ef57e1021100000001a33b4a85000000000000000000

1 output(s) for total of 337.606877202000 dcy

stealth address amount amount idx
00: 07b4ba4023b01bac1f0457ccf37f363a9ffa0cab2025195a2742e5f3d0dbec68 337.606877202000 143789 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": 78355, "vin": [ { "gen": { "height": 78345 } } ], "vout": [ { "amount": 337606877202, "target": { "key": "07b4ba4023b01bac1f0457ccf37f363a9ffa0cab2025195a2742e5f3d0dbec68" } } ], "extra": [ 1, 126, 124, 38, 238, 125, 148, 64, 194, 244, 189, 242, 89, 164, 233, 39, 72, 47, 68, 63, 145, 34, 87, 76, 241, 214, 179, 156, 228, 84, 239, 87, 225, 2, 17, 0, 0, 0, 1, 163, 59, 74, 133, 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