← previous blocknext block →recent activity
Analyzing
Block #106,207,268
35 transactions · 33 stateful · 2026-09-19 15:00:12 UTC
Parallelism
63/100
Blocked
70%
Avg conflicts / tx
1.66
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,207,268 · 35 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w08w19w210w011w112w214w315w416w517w618w719w828w130w231w333w1134w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x2f50c84a…3640
0x34b655…2a6f
10 touches
10 conflicts
0x3aca64ec…7cbb
0x34b655…2a6f
10 touches
10 conflicts
0x4fb437cc…05f7
0x34b655…2a6f
10 touches
10 conflicts
0x7499cc33…a306
0x34b655…2a6f
10 touches
10 conflicts
0x7eb3ae1e…a1a3
0x34b655…2a6f
10 touches
10 conflicts
0x88fc2a68…3918
0x34b655…2a6f
10 touches
10 conflicts
0x98dd86bb…1edb
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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity