← previous blocknext block →recent activity
Analyzing
Block #108,873,622
22 transactions · 18 stateful · 2026-09-28 22:47:20 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,873,622 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w27w08w19w110w211w313w414w515w616w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc6ea79…e2dc
0x34b655…2a6f
14 touches
21 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
10 touches
10 conflicts
0x2a8bc05a…0464
0x37db7f…ec7b
10 touches
10 conflicts
0xa93fef74…94b3
0x37db7f…ec7b
10 touches
10 conflicts
0xe3e67fe3…e754
0x37db7f…ec7b
10 touches
10 conflicts
0x237ae0f2…97d8
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x9fc6ea791d…ace2dc
Audit this contract →
← previous block·next block →recent activity