← previous blocknext block →recent activity
Analyzing
Block #105,922,640
20 transactions · 20 stateful · 2026-09-18 15:07:32 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,922,640 · 20 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
1w02w04w19w110w011w112w213w317w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e691068…4090
0x6f6493…b480
8 touches
6 conflicts
0xef6ca809…85b0
0x6f6493…b480
8 touches
6 conflicts
0x9094baa3…e564
0x6f6493…b480
8 touches
6 conflicts
0x8b88cc41…2afb
0x6f6493…b480
8 touches
6 conflicts
0x700b2b75…2748
0x6f6493…b480
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x52061a32…cc8b
0x34b655…2a6f
4 touches
1 conflict
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 0x6e6910682a…fb4090
Audit this contract →
← previous block·next block →recent activity