← previous blocknext block →recent activity
Analyzing
Block #106,187,469
22 transactions · 21 stateful · 2026-09-19 13:20:31 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,187,469 · 22 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
1w02w15w09w110w211w013w114w215w316w417w520w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046776c6…e120
0x34b655…2a6f
10 touches
10 conflicts
0x2d071de0…c86e
0x34b655…2a6f
10 touches
10 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
8 touches
6 conflicts
0xd62f3741…b903
0x34b655…2a6f
8 touches
6 conflicts
0x6c87effb…ca21
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xde6b17b7…bd1a
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 0x046776c66d…81e120
Audit this contract →
← previous block·next block →recent activity