← previous blocknext block →recent activity
Analyzing
Block #100,081,112
20 transactions · 19 stateful · 2026-08-29 03:48:41 UTC
Parallelism
75/100
Blocked
26%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,081,112 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w010w111w212w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa11b60f7…8e8b
0x34b655…2a6f
8 touches
6 conflicts
0x96a08475…54fe
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa7a6768d…8840
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x7aa91b8f…d070
0x2b46c0…1669
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
6 conflicts on slot 0xa11b60f7c7…f88e8b
Audit this contract →
← previous block·next block →recent activity