← previous blocknext block →recent activity
Analyzing
Block #106,467,029
20 transactions · 19 stateful · 2026-09-20 12:47:34 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,467,029 · 20 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
1w02w13w14w26w07w18w210w011w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe890a5b…ac60
0x34b655…2a6f
10 touches
10 conflicts
0x74e46435…fdcd
0x34b655…2a6f
10 touches
10 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
8 touches
6 conflicts
0xa8c7d195…3077
0x34b655…2a6f
8 touches
6 conflicts
0xad1d9367…3f9d
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 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 0xfe890a5b12…49ac60
Audit this contract →
← previous block·next block →recent activity