pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,813,197
← previous block
next block →
recent activity
Analyzing
Block #92,813,197
37 transactions · 28 stateful · 2026-08-03 15:42:05 UTC
Parallelism
76
/100
Blocked
54
%
Avg conflicts / tx
0.95
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,813,197
· 37 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#3
0x0c7abd22
#4
0x0c7abd22
#6
0x0c7abd22
#8
0x0c7abd22
#9
0x8263f5d9
#10
execPerpOps
#11
execPerpOps
#12
0x41a8f47c
#14
execFwdPositionOps
· blocks 4
#17
0x3f5c179b
#18
0x3f5c179b
#19
execOrders
#22
batchUpdate
#23
0xed82b078
· blocks 1
#25
0xe9316489
· blocks 1
#27
setData
#28
0xf4997f…a18b
#30
execOrders
#34
0x59558d29
· blocks 1
#36
0xc7e3ec2c
#2
0x0c7abd22
· blocks 3
#24
0xed82b078
#26
0xe9316489
#35
0x59558d29
#5
0x0c7abd22
· blocks 2
#7
0x0c7abd22
· blocks 1
#13
0x0c7abd22
· blocks 5
#15
execFwdPositionOps
· blocks 4
#29
execOrders
· blocks 3
#16
execFwdPositionOps
· blocks 3
#31
execOrders
· blocks 2
#20
execFwdPositionOps
#21
execFwdPositionOps
#32
execOrders
· blocks 1
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
7
w3
13
w4
14
w0
15
w5
16
w6
20
w7
21
w7
29
w5
31
w6
33
w8
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf776883…7718
0xd32edf…ff58
9 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x97216283…fd1d
0x34b655…2a6f
6 touches
3 conflicts
0xa03c2a35…52e6
0x34b655…2a6f
6 touches
3 conflicts
0x0d481dec…5ccd
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:
FastLane: FastLaneAuctionHandler
10 conflicts on slot
0xbf77688302…1e7718
Audit this contract →
← previous block
·
next block →
recent activity