← previous blocknext block →recent activity
Analyzing
Block #105,930,802
24 transactions · 23 stateful · 2026-09-18 15:48:38 UTC
Parallelism
63/100
Blocked
52%
Avg conflicts / tx
1.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,930,802 · 24 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
1w02w04w05w17w18w29w310w011w112w413w517w518w619w720w823w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x321da207…859d
0x34b655…2a6f
12 touches
15 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
6 touches
3 conflicts
0x2fba77e7…bea1
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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
15 conflicts on slot 0x321da20756…10859d
Audit this contract →
← previous block·next block →recent activity