← previous blocknext block →recent activity
Analyzing
Block #106,216,183
18 transactions · 18 stateful · 2026-09-19 15:45:05 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,216,183 · 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
1w02w03w15w06w17w18w29w213w314w315w416w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7039b016…1ab2
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x38c6ff01…689f
0x34b655…2a6f
8 touches
6 conflicts
0x2e90dcf9…1289
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x7039b016be…9c1ab2
Audit this contract →
← previous block·next block →recent activity