← previous blocknext block →recent activity
Analyzing
Block #90,820,054
19 transactions · 19 stateful · 2026-07-27 16:31:46 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,820,054 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w110w011w313w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd95eb4…e562
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x99479bc5…3a88
0x34b655…2a6f
6 touches
3 conflicts
0x4f267385…cc89
0x34b655…2a6f
4 touches
1 conflict
0x6c7cb3c8…71da
0x34b655…2a6f
4 touches
1 conflict
0x733de0a2…0690
0x34b655…2a6f
4 touches
1 conflict
0x7e162301…9c1b
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
10 conflicts on slot 0x0bd95eb406…f6e562
Audit this contract →
← previous block·next block →recent activity