← previous blocknext block →recent activity
Analyzing
Block #106,184,667
26 transactions · 25 stateful · 2026-09-19 13:06:25 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,184,667 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w19w211w013w220w321w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa3b4402…74e6
0x34b655…2a6f
10 touches
10 conflicts
0xdd69db8d…01e9
0xd32edf…ff58
7 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x0cc57183…219e
0x065c9d…c394
5 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x7322fb4a…635e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0xaa3b44023d…a974e6
Audit this contract →
← previous block·next block →recent activity