← previous blocknext block →recent activity
Analyzing
Block #106,468,672
18 transactions · 18 stateful · 2026-09-20 12:55:50 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,468,672 · 18 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
1w02w13w24w35w06w18w09w112w113w114w315w417w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
6 touches
3 conflicts
0x22187aaf…c0d5
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0x2e7d7640…5831
0x34b655…2a6f
6 touches
3 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
6 touches
3 conflicts
0x2559451e…537d
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
6 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity