← previous blocknext block →recent activity
Analyzing
Block #91,162,659
16 transactions · 15 stateful · 2026-07-28 21:16:14 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,162,659 · 16 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
4w05w16w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x4672a4ae…e965
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0x1346ac01…31f2
0x34b655…2a6f
2 touches
0 conflicts
0x26dda7d6…8c4d
0x34b655…2a6f
2 touches
0 conflicts
0x36ccd82a…7be7
0x34b655…2a6f
2 touches
0 conflicts
0x3e2663d3…a620
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: 0x48cba278…e2b48b
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity