← previous blocknext block →recent activity
Analyzing
Block #91,111,508
13 transactions · 13 stateful · 2026-07-28 16:58:56 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,111,508 · 13 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
1w02w14w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f97aa17…6776
0x34b655…2a6f
8 touches
6 conflicts
0x673e2e56…9f5d
0x34b655…2a6f
6 touches
3 conflicts
0xd80a37f7…9691
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5fab7fbe…1ce5
0x34b655…2a6f
4 touches
1 conflict
0xcd171c53…ebb1
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0x4f97aa17eb…2d6776
Audit this contract →
← previous block·next block →recent activity