← previous blocknext block →recent activity
Analyzing
Block #106,932,143
19 transactions · 18 stateful · 2026-09-22 03:49:31 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,932,143 · 19 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
1w02w03w16w07w18w29w310w411w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
12 touches
15 conflicts
0x94e7f277…471b
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x251ee419…4404
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x8fb6bad3…adeb
0x34b655…2a6f
10 touches
10 conflicts
0xc8cdbe8c…bd54
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
15 conflicts on slot 0x7098645134…3ac6bd
Audit this contract →
← previous block·next block →recent activity