← previous blocknext block →recent activity

Analyzing

Block #93,150,013

12 transactions · 11 stateful · 2026-08-04 19:57:57 UTC

Parallelism

67/100

Blocked

55%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,150,013  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xb5a3b1be…8122

0x34b655…2a6f

6 touches
3 conflicts

0xa0d70a98…d179

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x4755fafb…859b

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4dee3f71…642a

0x34b655…2a6f

4 touches
1 conflict

0x747f609d…1555

0x34b655…2a6f

4 touches
1 conflict

0x772ab420…c2f6

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Perpl

3 conflicts on slot 0xb5a3b1be7c…288122

← previous block·next block →recent activity