← previous blocknext block →recent activity
Analyzing
Block #91,064,004
10 transactions · 10 stateful · 2026-07-28 12:59:52 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,064,004 · 10 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
3w04w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d94d7d6…6ed4
0x34b655…2a6f
4 touches
1 conflict
0x983e6564…18eb
0x34b655…2a6f
4 touches
1 conflict
0x9b5f80e5…d4a6
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x434587c7…2645
0x34b655…2a6f
2 touches
0 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
2 touches
0 conflicts
0x5cfa06bc…87fb
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
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 0x6d94d7d6d7…ed6ed4
Audit this contract →
← previous block·next block →recent activity