← previous blocknext block →recent activity
Analyzing
Block #91,063,680
14 transactions · 14 stateful · 2026-07-28 12:58:14 UTC
Parallelism
79/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,063,680 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x183a32c3…5ef2
0x34b655…2a6f
2 touches
0 conflicts
0x19d0122b…937c
0x34b655…2a6f
2 touches
0 conflicts
0x3d22c439…de6d
0x34b655…2a6f
2 touches
0 conflicts
0x59052228…add7
0x34b655…2a6f
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
1 conflict on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity