← previous blocknext block →recent activity
Analyzing
Block #106,370,228
21 transactions · 20 stateful · 2026-09-20 04:40:20 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,370,228 · 21 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
1w02w03w07w08w19w210w311w112w013w115w218w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0010353a…b951
0x6f6493…b480
8 touches
6 conflicts
0x0033b9a7…c871
0x6f6493…b480
8 touches
6 conflicts
0x05e830cc…86b3
0x6f6493…b480
8 touches
6 conflicts
0x11ea552e…f388
0x6f6493…b480
8 touches
6 conflicts
0x22ccadae…0d65
0x6f6493…b480
8 touches
6 conflicts
0x2fc7fbe7…2b11
0x6f6493…b480
8 touches
6 conflicts
0x310cb0ed…fe2c
0x6f6493…b480
8 touches
6 conflicts
0x329a404a…4741
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 0x0010353ab4…e9b951
Audit this contract →
← previous block·next block →recent activity