← previous blocknext block →recent activity
Analyzing
Block #106,184,813
25 transactions · 24 stateful · 2026-09-19 13:07:09 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,184,813 · 25 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
3w04w05w18w09w010w112w113w214w315w419w520w623w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaa2c379…6b11
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xd62f3741…b903
0x34b655…2a6f
6 touches
3 conflicts
0x046776c6…e120
0x34b655…2a6f
6 touches
3 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
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: Perpl
15 conflicts on slot 0xfaa2c379ab…786b11
Audit this contract →
← previous block·next block →recent activity