← previous blocknext block →recent activity
Analyzing
Block #106,100,061
11 transactions · 11 stateful · 2026-09-19 06:00:37 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,100,061 · 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
2w03w14w25w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b2
0x37db7f…ec7b
8 touches
6 conflicts
0x6286219a…0721
0x37db7f…ec7b
6 touches
3 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
4 touches
1 conflict
0xb127c451…050a
0x37db7f…ec7b
4 touches
1 conflict
0x6c68ddc9…d106
0x37db7f…ec7b
4 touches
1 conflict
0x9ba10aad…9bc5
0x34b655…2a6f
4 touches
1 conflict
0x7f430e47…4cbd
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1ac
0x37db7f…ec7b
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: 0x37db7fbf…3eec7b
6 conflicts on slot 0x8a35acfbc1…6bd1b2
Audit this contract →
← previous block·next block →recent activity