← previous blocknext block →recent activity
Analyzing
Block #106,474,213
23 transactions · 22 stateful · 2026-09-20 13:23:43 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,474,213 · 23 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
1w02w13w04w110w011w113w114w215w216w317w018w320w421w222w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03ab4c58…684f
0x34b655…2a6f
8 touches
6 conflicts
0xa242e227…2e45
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
8 touches
6 conflicts
0x8e7695d2…21ed
0x34b655…2a6f
8 touches
6 conflicts
0xde94a368…95d1
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x0de7749d…5bef
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 0x03ab4c5819…46684f
Audit this contract →
← previous block·next block →recent activity