← previous blocknext block →recent activity
Analyzing
Block #106,100,341
93 transactions · 92 stateful · 2026-09-19 06:02:02 UTC
Parallelism
94/100
Blocked
11%
Avg conflicts / tx
0.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,100,341 · 93 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w36w411w012w113w289w190w391w492w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
10 touches
10 conflicts
0x93979174…1832
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x556beb43…e627
0x34b655…2a6f
6 touches
3 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
6 touches
3 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity