← previous blocknext block →recent activity
Analyzing
Block #91,164,842
9 transactions · 8 stateful · 2026-07-28 21:27:13 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,164,842 · 9 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
1w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x19439a65…eb51
0x34b655…2a6f
4 touches
1 conflict
0x64158499…e370
0x34b655…2a6f
4 touches
1 conflict
0xfa3d71b4…937f
0x34b655…2a6f
4 touches
1 conflict
0xf5b23754…5eb1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity