Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 386beb7c8b183a1dbd1e235408cd7cc410a7f07af7f136cb9d9dd07c9e45ba20

Tx prefix hash: 68707f9c6d9e0d03fb6b8dab526ae9b4119b1916711b1fb248232c2ddfa17c1a
Tx public key: 1ec1ae798cd9550370204f293cb79ae5719d3369fd5c6cc554d35fa29f7c9a3b
Timestamp: 1635265268 Timestamp [UCT]: 2021-10-26 16:21:08 Age [y:d:h:m:s]: 03:061:15:35:02
Block: 360967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 822486 RingCT/type: yes/0
Extra: 011ec1ae798cd9550370204f293cb79ae5719d3369fd5c6cc554d35fa29f7c9a3b02110000000406faf294000000000000000000

1 output(s) for total of 39.081110156000 dcy

stealth address amount amount idx
00: 46377a005c21462768f3d251ae906af80709cdc285086fd9f96bcc1c17aea75c 39.081110156000 734550 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": 360977, "vin": [ { "gen": { "height": 360967 } } ], "vout": [ { "amount": 39081110156, "target": { "key": "46377a005c21462768f3d251ae906af80709cdc285086fd9f96bcc1c17aea75c" } } ], "extra": [ 1, 30, 193, 174, 121, 140, 217, 85, 3, 112, 32, 79, 41, 60, 183, 154, 229, 113, 157, 51, 105, 253, 92, 108, 197, 84, 211, 95, 162, 159, 124, 154, 59, 2, 17, 0, 0, 0, 4, 6, 250, 242, 148, 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