← previous blocknext block →recent activity
Analyzing
Block #106,336,191
9 transactions · 9 stateful · 2026-09-20 01:49:02 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,336,191 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c8a09c1…16e3
0x6f6493…b480
6 touches
3 conflicts
0x1a56ff2e…ebf1
0x6f6493…b480
6 touches
3 conflicts
0x1bcf157c…b302
0x6f6493…b480
6 touches
3 conflicts
0x229bd88c…fe89
0x6f6493…b480
6 touches
3 conflicts
0x24a1a112…9348
0x6f6493…b480
6 touches
3 conflicts
0x281693b5…837c
0x6f6493…b480
6 touches
3 conflicts
0x3560931e…d52c
0x6f6493…b480
6 touches
3 conflicts
0x3febb8a9…06c7
0x6f6493…b480
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: 0x6f6493e3…08b480
3 conflicts on slot 0x0c8a09c14e…9f16e3
Audit this contract →
← previous block·next block →recent activity