← previous blocknext block →recent activity
Analyzing
Block #107,824,279
26 transactions · 22 stateful · 2026-09-25 06:42:25 UTC
Parallelism
92/100
Blocked
32%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,824,279 · 26 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w08w09w110w013w117w018w119w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c3773f9…8c3a
0x34b655…2a6f
4 touches
1 conflict
0x6cee7b24…2ebf
0x34b655…2a6f
4 touches
1 conflict
0x744dd823…909f
0x34b655…2a6f
4 touches
1 conflict
0xaf7f13f9…a2c9
0x34b655…2a6f
4 touches
1 conflict
0x3a663e9a…a9ca
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9cb
0x508254…98bd
4 touches
1 conflict
0xe2995197…337c
0x860869…ff01
4 touches
1 conflict
0xe2995197…337c
0xcc9410…4c10
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
1 conflict on slot 0x4c3773f959…648c3a
Audit this contract →
← previous block·next block →recent activity