← previous blocknext block →recent activity
Analyzing
Block #91,765,374
19 transactions · 18 stateful · 2026-07-30 23:50:35 UTC
Parallelism
58/100
Blocked
39%
Avg conflicts / tx
0.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,765,374 · 19 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
1w02w03w16w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2ed336a4…72b1
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0xc4d2090a…60ed
0x34b655…2a6f
6 touches
3 conflicts
0xf1e05474…a3c6
0x34b655…2a6f
5 touches
3 conflicts
0x86977b3d…a9c4
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity