← previous blocknext block →recent activity
Analyzing
Block #91,396,849
16 transactions · 14 stateful · 2026-07-29 16:55:25 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,396,849 · 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
6w07w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0xb852cf41…12b6
0x34b655…2a6f
4 touches
1 conflict
0x0caa5e3f…ea20
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x0aa9bd…5d57
2 touches
0 conflicts
0x00000000…000c
0x0aa9bd…5d57
2 touches
0 conflicts
0x2b51d4a1…acc3
0x3bd359…433a
2 touches
0 conflicts
0xb4e825af…69e0
0x3bd359…433a
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 0xa3ed5a0966…25c6d3
Audit this contract →
← previous block·next block →recent activity