← previous blocknext block →recent activity
Analyzing
Block #106,186,161
24 transactions · 20 stateful · 2026-09-19 13:13:56 UTC
Parallelism
71/100
Blocked
60%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,186,161 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w28w213w014w115w316w417w418w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9bfdf60…1d24
0x34b655…2a6f
8 touches
6 conflicts
0x05e1eba1…6491
0x34b655…2a6f
8 touches
6 conflicts
0x0de7749d…5bef
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
8 touches
6 conflicts
0x1df07d43…ff95
0x34b655…2a6f
8 touches
6 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0xf9bfdf6025…441d24
Audit this contract →
← previous block·next block →recent activity