← previous blocknext block →recent activity
Analyzing
Block #106,046,138
20 transactions · 20 stateful · 2026-09-19 01:29:15 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,046,138 · 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
1w02w13w26w07w110w011w012w113w214w315w117w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04033c9a…e941
0x6f6493…b480
8 touches
6 conflicts
0x07bccaeb…9325
0x6f6493…b480
8 touches
6 conflicts
0x1124683a…2b5b
0x6f6493…b480
8 touches
6 conflicts
0x1aa3d799…a59e
0x6f6493…b480
8 touches
6 conflicts
0x1aa3d799…a5a2
0x6f6493…b480
8 touches
6 conflicts
0x1dd8a04d…f8d8
0x6f6493…b480
8 touches
6 conflicts
0x1f4f65d3…7de3
0x6f6493…b480
8 touches
6 conflicts
0x38de355e…9edc
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 0x04033c9a4c…cfe941
Audit this contract →
← previous block·next block →recent activity