← previous blocknext block →recent activity
Analyzing
Block #90,772,863
16 transactions · 14 stateful · 2026-07-27 12:34:13 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,772,863 · 16 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
1w03w14w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0x0aa54240…f89e
0x34b655…2a6f
2 touches
0 conflicts
0x134cc376…7c80
0x34b655…2a6f
2 touches
0 conflicts
0x171aa816…71e8
0x34b655…2a6f
2 touches
0 conflicts
0x36ccd82a…7be7
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
6 conflicts on slot 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity