← previous blocknext block →recent activity
Analyzing
Block #106,810,244
19 transactions · 17 stateful · 2026-09-21 17:35:57 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
1.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,810,244 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w08w29w310w411w512w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01f19c33…170d
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x48aea44b…fca0
0x34b655…2a6f
10 touches
10 conflicts
0x92c3ce15…70cc
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa242e227…2e45
0x34b655…2a6f
6 touches
3 conflicts
0x072f1563…3e73
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x01f19c3396…f1170d
Audit this contract →
← previous block·next block →recent activity