← previous blocknext block →recent activity
Analyzing
Block #91,132,495
12 transactions · 12 stateful · 2026-07-28 18:44:30 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,132,495 · 12 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x02b62ce6…d449
0x34b655…2a6f
2 touches
0 conflicts
0x0ca3397e…3644
0x34b655…2a6f
2 touches
0 conflicts
0x10981d9e…6ebc
0x34b655…2a6f
2 touches
0 conflicts
0x17e99ec0…5c17
0x34b655…2a6f
2 touches
0 conflicts
0x1bf8d2af…d140
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 0x845ec8b071…13c1af
Audit this contract →
← previous block·next block →recent activity