← previous blocknext block →recent activity
Analyzing
Block #91,130,854
9 transactions · 8 stateful · 2026-07-28 18:36:14 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,130,854 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x1cc2362d…1fb1
0x34b655…2a6f
2 touches
0 conflicts
0x27b638a0…761d
0x34b655…2a6f
2 touches
0 conflicts
0x32b7e349…5f63
0x34b655…2a6f
2 touches
0 conflicts
0x3a823597…b343
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity