← previous blocknext block →recent activity
Analyzing
Block #91,975,407
22 transactions · 21 stateful · 2026-07-31 17:27:14 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,975,407 · 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
1w03w05w16w17w28w39w210w312w114w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbffde283…3385
0x34b655…2a6f
10 touches
10 conflicts
0xda27c764…7fab
0x34b655…2a6f
6 touches
3 conflicts
0x7b55198a…b946
0x34b655…2a6f
6 touches
3 conflicts
0x874de4b7…9606
0x34b655…2a6f
5 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
4 touches
1 conflict
0xb5f244d5…f550
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity