← previous blocknext block →recent activity
Analyzing
Block #91,159,307
13 transactions · 13 stateful · 2026-07-28 20:59:23 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,159,307 · 13 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
1w02w16w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70b7b52e…7744
0x34b655…2a6f
4 touches
1 conflict
0x9711d99c…3d4c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xfa2638bb…e46f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1c3295fd…097a
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
1 conflict on slot 0x70b7b52e5b…0a7744
Audit this contract →
← previous block·next block →recent activity