← previous blocknext block →recent activity
Analyzing
Block #106,481,709
20 transactions · 17 stateful · 2026-09-20 14:01:26 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,481,709 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w29w012w313w414w517w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8fab3e2…3dda
0x34b655…2a6f
10 touches
10 conflicts
0x33365a6a…7e0b
0x34b655…2a6f
8 touches
6 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5906754f…b584
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0xebe581d8…2696
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
10 conflicts on slot 0xe8fab3e2e4…fc3dda
Audit this contract →
← previous block·next block →recent activity