pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,506,172
← previous block
next block →
recent activity
Analyzing
Block #93,506,172
10 transactions · 10 stateful · 2026-08-06 01:48:37 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,506,172
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
· blocks 1
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x6a73e86c
#8
setData
#3
0x915df74d
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x4e4fd9e7…e6be
0x40c49f…2af0
2 touches
0 conflicts
0x5579cc0d…75cb
0x40c49f…2af0
2 touches
0 conflicts
0x5d601639…d720
0x5dd8f3…c69c
2 touches
0 conflicts
0x122ec7eb…c568
0x754704…b603
2 touches
0 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
1 conflict on slot
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity