← previous blocknext block →recent activity
Analyzing
Block #103,210,750
18 transactions · 16 stateful · 2026-09-09 02:52:17 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,210,750 · 18 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
1w02w13w14w210w311w413w015w116w017w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0x9b924b5c…2ae5
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
6 touches
3 conflicts
0x2f17174f…68b4
0x34b655…2a6f
6 touches
3 conflicts
0xdac8e13c…bc65
0x34b655…2a6f
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
10 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity