← previous blocknext block →recent activity
Analyzing
Block #91,134,365
12 transactions · 11 stateful · 2026-07-28 18:53:54 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,134,365 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x159cff26…7665
0x34b655…2a6f
6 touches
3 conflicts
0x849cb897…43de
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x50e616e2…8782
0x34b655…2a6f
4 touches
1 conflict
0x6db21da6…cfde
0x34b655…2a6f
4 touches
1 conflict
0x9ad8105e…4795
0x34b655…2a6f
4 touches
1 conflict
0xa524a39b…df24
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 0x159cff262c…e57665
Audit this contract →
← previous block·next block →recent activity