← previous blocknext block →recent activity
Analyzing
Block #106,234,866
25 transactions · 22 stateful · 2026-09-19 17:19:09 UTC
Parallelism
80/100
Blocked
55%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,234,866 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w28w39w410w011w114w015w116w117w118w019w120w222w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b5
0x37db7f…ec7b
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1b4
0x37db7f…ec7b
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x56f91464…1e91
0x37db7f…ec7b
4 touches
1 conflict
0x640481cc…a2df
0x37db7f…ec7b
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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
10 conflicts on slot 0x8a35acfbc1…6bd1b5
Audit this contract →
← previous block·next block →recent activity