← previous blocknext block →recent activity
Analyzing
Block #103,050,587
16 transactions · 16 stateful · 2026-09-08 13:24:41 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,050,587 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77382e7c…d44b
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x25180879…8191
0x34b655…2a6f
4 touches
1 conflict
0xb358a740…cf65
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x9c2fc330…0091
0x34b655…2a6f
2 touches
0 conflicts
0xb6af9a17…f444
0x34b655…2a6f
2 touches
0 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x77382e7cdf…3cd44b
Audit this contract →
← previous block·next block →recent activity