← previous blocknext block →recent activity
Analyzing
Block #91,396,044
14 transactions · 13 stateful · 2026-07-29 16:51:21 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,396,044 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w38w19w010w111w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x10b7971b…3ba4
0x34b655…2a6f
4 touches
1 conflict
0x1dd79365…4bab
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad05
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad07
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity