← previous blocknext block →recent activity
Analyzing
Block #91,000,793
13 transactions · 11 stateful · 2026-07-28 07:41:28 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,000,793 · 13 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
1w02w16w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb674fb5…9393
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x67a56c8b…f955
0x34b655…2a6f
6 touches
3 conflicts
0x9e7f288e…1a24
0x34b655…2a6f
4 touches
1 conflict
0x641aed07…bcb9
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x615e7c53…e353
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 0xcb674fb588…009393
Audit this contract →
← previous block·next block →recent activity