pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,420,342
← previous block
next block →
recent activity
Analyzing
Block #93,420,342
10 transactions · 7 stateful · 2026-08-05 18:37:08 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,420,342
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x3f5c179b
#3
forward
#4
batchCancelOrders
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xb452ca…193b
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc21d7c…e062
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x007dc60b…a97a
0x34b655…2a6f
2 touches
0 conflicts
0x0728ec77…146c
0x34b655…2a6f
2 touches
0 conflicts
0x0c8789a6…73ef
0x34b655…2a6f
2 touches
0 conflicts
0x0e2ca475…e91d
0x34b655…2a6f
2 touches
0 conflicts
0x12d581a6…c9e6
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
0xdfc21d7c53…51e062
Audit this contract →
← previous block
·
next block →
recent activity