← previous blocknext block →recent activity
Analyzing
Block #106,533,342
26 transactions · 23 stateful · 2026-09-20 18:21:19 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,533,342 · 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
1w02w13w14w212w213w314w315w417w018w122w123w225w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa08efe82…5d69
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0x5c8a6a62…78e2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
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
6 conflicts on slot 0xa08efe8229…6f5d69
Audit this contract →
← previous block·next block →recent activity