← previous blocknext block →recent activity
Analyzing
Block #106,276,035
34 transactions · 31 stateful · 2026-09-19 20:46:20 UTC
Parallelism
74/100
Blocked
61%
Avg conflicts / tx
1.47
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,276,035 · 34 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w126w427w528w629w730w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c00c56d…fd1f
0x34b655…2a6f
16 touches
28 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x28d91d54…9079
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x5e2ea201…12de
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
28 conflicts on slot 0x0c00c56daa…a9fd1f
Audit this contract →
← previous block·next block →recent activity