← previous blocknext block →recent activity
Analyzing
Block #106,533,889
16 transactions · 16 stateful · 2026-09-20 18:24:04 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,533,889 · 16 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
1w02w13w14w27w08w19w210w311w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15f31422…c39a
0x34b655…2a6f
8 touches
6 conflicts
0x51799411…9ca7
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0xd193364c…cd91
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
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 0x15f31422d3…60c39a
Audit this contract →
← previous block·next block →recent activity