← previous blocknext block →recent activity
Analyzing
Block #91,137,943
9 transactions · 8 stateful · 2026-07-28 19:11:54 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,137,943 · 9 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
1w02w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd58b9a66…1c23
0x34b655…2a6f
6 touches
3 conflicts
0x3e4af36e…07ae
0x34b655…2a6f
4 touches
1 conflict
0x8d420fcb…f7b7
0x34b655…2a6f
4 touches
1 conflict
0xa54af5db…2aa8
0x34b655…2a6f
4 touches
1 conflict
0xab17a6c2…ee9a
0x34b655…2a6f
4 touches
1 conflict
0xd01910c9…9418
0x34b655…2a6f
4 touches
1 conflict
0xd2e35622…f491
0x34b655…2a6f
4 touches
1 conflict
0xd4702f73…926c
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 0xd58b9a66f8…5f1c23
Audit this contract →
← previous block·next block →recent activity