← previous blocknext block →recent activity
Analyzing
Block #108,279,194
18 transactions · 18 stateful · 2026-09-26 20:52:00 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,279,194 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w19w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x038b9243…553d
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x8639476f…c672
0x34b655…2a6f
6 touches
3 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0x2a8bc05a…0464
0x37db7f…ec7b
4 touches
1 conflict
0xa93fef74…94b3
0x37db7f…ec7b
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 0x038b92433d…c5553d
Audit this contract →
← previous block·next block →recent activity