← previous blocknext block →recent activity
Analyzing
Block #106,385,588
21 transactions · 19 stateful · 2026-09-20 05:57:39 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,385,588 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w311w312w413w414w515w616w719w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e665745…8517
0x34b655…2a6f
14 touches
21 conflicts
0xba33378a…f1df
0x34b655…2a6f
10 touches
10 conflicts
0x7462b8f2…6312
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x51d607f1…6458
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x947bb79d…6458
0x34b655…2a6f
6 touches
3 conflicts
0xa60eabc0…9f8c
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 0x1e66574536…6d8517
Audit this contract →
← previous block·next block →recent activity