← previous blocknext block →recent activity
Analyzing
Block #91,782,000
22 transactions · 20 stateful · 2026-07-31 01:14:14 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,782,000 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w16w211w312w413w514w617w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46e558af…7871
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xfc3d5171…8357
0x34b655…2a6f
8 touches
6 conflicts
0x917f99a5…7989
0x34b655…2a6f
8 touches
6 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0x99701186…1cbf
0x34b655…2a6f
6 touches
3 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x46e558afdd…aa7871
Audit this contract →
← previous block·next block →recent activity