← previous blocknext block →recent activity
Analyzing
Block #91,002,712
14 transactions · 13 stateful · 2026-07-28 07:51:12 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,002,712 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w110w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53cccb07…d7f0
0x34b655…2a6f
4 touches
1 conflict
0x947f1921…b1ba
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xdc794a06…1a89
0xd32edf…ff58
3 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xc0a026fc…1a03
0x065c9d…c394
2 touches
0 conflicts
0xe8df1a85…cefe
0x065c9d…c394
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 0x53cccb0751…4fd7f0
Audit this contract →
← previous block·next block →recent activity