pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,399,817
← previous block
next block →
recent activity
Analyzing
Block #93,399,817
9 transactions · 9 stateful · 2026-08-05 16:53:56 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,399,817
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeb282f7f
#2
execFwdPositionOps
· blocks 1
#3
0x3f5c179b
#5
0x6a736b1c
#6
0xd708c5d8
#7
setData
#8
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe768012…b65e
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9ef
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9f0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa294c621…7eec
0x34b655…2a6f
4 touches
1 conflict
0xca145e39…0673
0x34b655…2a6f
3 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
2 touches
0 conflicts
0xd8eb2d31…2ac0
0xea1b8e…c5ec
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
0xfe76801205…69b65e
Audit this contract →
← previous block
·
next block →
recent activity