← previous blocknext block →recent activity
Analyzing
Block #90,459,424
16 transactions · 16 stateful · 2026-07-26 10:17:26 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,459,424 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w010w012w213w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4610db8…cad4
0x34b655…2a6f
6 touches
3 conflicts
0x7624b9d6…59e6
0x34b655…2a6f
6 touches
3 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0xf6366f16…1d91
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0933b65e…e7d4
0x34b655…2a6f
4 touches
1 conflict
0x5770813f…1aa7
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
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 0xa4610db8f7…f8cad4
Audit this contract →
← previous block·next block →recent activity