← previous blocknext block →recent activity
Analyzing
Block #106,397,134
23 transactions · 23 stateful · 2026-09-20 06:55:45 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
2.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,397,134 · 23 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
1w02w13w04w05w16w18w29w312w313w414w415w516w617w720w522w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e1c23e9…4f81
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xb37a85c9…4f4b
0x34b655…2a6f
10 touches
10 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x6cab9ef4…f849
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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 0x5e1c23e9cd…6d4f81
Audit this contract →
← previous block·next block →recent activity