← previous blocknext block →recent activity
Analyzing
Block #91,763,621
21 transactions · 19 stateful · 2026-07-30 23:41:46 UTC
Parallelism
81/100
Blocked
63%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,763,621 · 21 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
1w02w13w25w26w07w18w19w210w212w213w316w017w118w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2ee54a3…ff75
0x34b655…2a6f
6 touches
3 conflicts
0x6f58168d…ea24
0x34b655…2a6f
6 touches
3 conflicts
0x7b8368aa…9d5d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x77a5bf11…c143
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x794b8f81…3ead
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xf2ee54a3b7…08ff75
Audit this contract →
← previous block·next block →recent activity