pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,509,551
← previous block
next block →
recent activity
Analyzing
Block #93,509,551
9 transactions · 7 stateful · 2026-08-06 02:05:36 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,509,551
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketBuy
#5
placeAndExecuteMarketBuy
· blocks 1
#7
execFwdPositionOps
· blocks 1
#6
placeAndExecuteMarketSell
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x547a4d58…34ee
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x5e8223c2…c242
0x34b655…2a6f
2 touches
0 conflicts
0xe0f449fb…30e9
0x34b655…2a6f
2 touches
0 conflicts
0xf95f86cd…e927
0x34b655…2a6f
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
0x547a4d5885…1934ee
Audit this contract →
← previous block
·
next block →
recent activity