← previous blocknext block →recent activity
Analyzing
Block #91,138,002
19 transactions · 18 stateful · 2026-07-28 19:12:12 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,138,002 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w511w012w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe3d2a2f…6b7b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x09775041…3e77
0x34b655…2a6f
6 touches
3 conflicts
0x4a6b3039…6a98
0x34b655…2a6f
6 touches
3 conflicts
0xa2c4ca04…d47b
0x34b655…2a6f
4 touches
1 conflict
0xb46bb9bf…deb7
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 0xfe3d2a2f17…206b7b
Audit this contract →
← previous block·next block →recent activity