← previous blocknext block →recent activity
Analyzing
Block #101,658,869
18 transactions · 16 stateful · 2026-09-03 16:11:28 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,658,869 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w19w110w212w216w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d99a6e0…be0e
0x34b655…2a6f
6 touches
3 conflicts
0xf15f2fd5…c971
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe01158fd…f980
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
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
3 conflicts on slot 0x5d99a6e0f3…62be0e
Audit this contract →
← previous block·next block →recent activity