← previous blocknext block →recent activity
Analyzing
Block #105,748,847
11 transactions · 11 stateful · 2026-09-18 00:30:33 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,748,847 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0031082f…6478
0x6f6493…b480
8 touches
6 conflicts
0x006aba3d…f01f
0x6f6493…b480
8 touches
6 conflicts
0x0a045d82…a1b8
0x6f6493…b480
8 touches
6 conflicts
0x0bdc33bb…903e
0x6f6493…b480
8 touches
6 conflicts
0x0dd1065c…c83d
0x6f6493…b480
8 touches
6 conflicts
0x141fc9a8…080d
0x6f6493…b480
8 touches
6 conflicts
0x1933f43b…efc9
0x6f6493…b480
8 touches
6 conflicts
0x1bd1d15b…339c
0x6f6493…b480
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: 0x6f6493e3…08b480
6 conflicts on slot 0x0031082f86…226478
Audit this contract →
← previous block·next block →recent activity