← previous blocknext block →recent activity
Analyzing
Block #91,408,859
13 transactions · 13 stateful · 2026-07-29 17:56:06 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,408,859 · 13 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
3w06w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bb46f6c…7693
0x34b655…2a6f
4 touches
1 conflict
0x0cab691e…74a5
0x34b655…2a6f
4 touches
1 conflict
0xaeec27ec…4e33
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xfb874a6c…caa0
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x5e4b65e1…ebe1
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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 0x5bb46f6c35…937693
Audit this contract →
← previous block·next block →recent activity