← previous blocknext block →recent activity
Analyzing
Block #106,377,476
22 transactions · 20 stateful · 2026-09-20 05:16:49 UTC
Parallelism
68/100
Blocked
30%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,377,476 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w113w214w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b3d9f0a…5036
0x34b655…2a6f
14 touches
21 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
8 touches
6 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xa86b6726…f350
0x34b655…2a6f
6 touches
3 conflicts
0x961c0cd9…0937
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
21 conflicts on slot 0x4b3d9f0ae1…0e5036
Audit this contract →
← previous block·next block →recent activity