← previous blocknext block →recent activity
Analyzing
Block #100,609,121
26 transactions · 20 stateful · 2026-08-31 00:09:35 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,609,121 · 26 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
3w04w15w26w310w011w412w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc81faf7…1417
0x34b655…2a6f
10 touches
10 conflicts
0x74af0022…8c2a
0x34b655…2a6f
10 touches
10 conflicts
0xb4e24275…64cb
0x34b655…2a6f
8 touches
6 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
8 touches
6 conflicts
0x155e52ca…fac7
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xfc81faf76e…be1417
Audit this contract →
← previous block·next block →recent activity