← previous blocknext block →recent activity
Analyzing
Block #91,097,470
23 transactions · 21 stateful · 2026-07-28 15:48:18 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,097,470 · 23 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
1w03w04w15w06w17w18w19w110w212w214w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x61c2f688…cfbd
0x34b655…2a6f
4 touches
1 conflict
0x69aed638…fbf5
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x71e39e15…640b
0x34b655…2a6f
4 touches
1 conflict
0x78b60ad8…8468
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity