← previous blocknext block →recent activity
Analyzing
Block #91,164,537
12 transactions · 11 stateful · 2026-07-28 21:25:41 UTC
Parallelism
58/100
Blocked
55%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,164,537 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w39w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfeb9fc78…3c57
0x34b655…2a6f
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x51428ba4…83e1
0x34b655…2a6f
4 touches
1 conflict
0x570bb566…0f21
0x34b655…2a6f
4 touches
1 conflict
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x6f8644f7…10fa
0x34b655…2a6f
4 touches
1 conflict
0x7c3d51a9…db35
0x34b655…2a6f
4 touches
1 conflict
0x7c3d51a9…db36
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
1 conflict on slot 0xfeb9fc7895…993c57
Audit this contract →
← previous block·next block →recent activity