← previous blocknext block →recent activity
Analyzing
Block #106,568,464
16 transactions · 16 stateful · 2026-09-20 21:18:04 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,568,464 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w210w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20b1228b…2487
0x34b655…2a6f
6 touches
3 conflicts
0xcf6501e3…360c
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x4de0d8…bfc3
4 touches
1 conflict
0x7e32f1e0…5612
0x4de0d8…bfc3
4 touches
1 conflict
0xd3f1dc40…259b
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf3
0x4de0d8…bfc3
4 touches
1 conflict
0xefba3db1…114e
0x4de0d8…bfc3
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
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 0x20b1228bdf…a72487
Audit this contract →
← previous block·next block →recent activity