← previous blocknext block →recent activity
Analyzing
Block #91,423,454
25 transactions · 18 stateful · 2026-07-29 19:09:38 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,423,454 · 25 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
1w02w13w05w16w07w111w012w114w016w219w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x747f609d…1555
0x34b655…2a6f
6 touches
3 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdb9ae7ce…32b3
0x34b655…2a6f
6 touches
3 conflicts
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
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 0x747f609d18…eb1555
Audit this contract →
← previous block·next block →recent activity