← previous blocknext block →recent activity
Analyzing
Block #101,310,039
27 transactions · 26 stateful · 2026-09-02 10:56:23 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.07
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,310,039 · 27 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w411w212w315w016w317w118w520w121w022w123w224w626w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d4774…8b1c
0x34b655…2a6f
8 touches
6 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd4230a60…bd13
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf48fa71e…bb52
0x34b655…2a6f
6 touches
3 conflicts
0x24025143…5c6b
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 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 0xec7d4774db…558b1c
Audit this contract →
← previous block·next block →recent activity