← previous blocknext block →recent activity
Analyzing
Block #100,143,698
11 transactions · 11 stateful · 2026-08-29 09:03:57 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,143,698 · 11 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
1w03w05w16w27w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0xe0eda1d1…28ff
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x21844058…bc4a
0x34b655…2a6f
4 touches
1 conflict
0x7b42f6a7…f49c
0x34b655…2a6f
4 touches
1 conflict
0x809e4ebb…a01f
0x34b655…2a6f
4 touches
1 conflict
0x91cdfdeb…7feb
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 0x676f9f01ee…dea8ac
Audit this contract →
← previous block·next block →recent activity