← previous blocknext block →recent activity
Analyzing
Block #91,013,029
14 transactions · 13 stateful · 2026-07-28 08:43:23 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,013,029 · 14 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
5w06w07w19w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95dd1dda…bc0e
0x34b655…2a6f
6 touches
3 conflicts
0x299c0f04…09cf
0x34b655…2a6f
4 touches
1 conflict
0x2c7f2108…99fc
0x34b655…2a6f
4 touches
1 conflict
0x2c7f2108…99fd
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0x4672a4ae…e965
0x34b655…2a6f
4 touches
1 conflict
0x4a374a3f…1e8c
0x34b655…2a6f
4 touches
1 conflict
0x4e169881…8c80
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 0x95dd1ddad2…f7bc0e
Audit this contract →
← previous block·next block →recent activity