← previous blocknext block →recent activity
Analyzing
Block #100,118,650
11 transactions · 11 stateful · 2026-08-29 06:57:42 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,118,650 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w010w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8a8db2…8a6d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
2 touches
0 conflicts
0x37a5d2b7…25f0
0x34b655…2a6f
2 touches
0 conflicts
0x3986aba7…7d22
0x34b655…2a6f
2 touches
0 conflicts
0x3accf018…2e8b
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x5c8a8db2ad…f58a6d
Audit this contract →
← previous block·next block →recent activity