pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,556,065
← previous block
next block →
recent activity
Analyzing
Block #93,556,065
11 transactions · 11 stateful · 2026-08-06 05:59:25 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,556,065
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
0x5acec890
· blocks 2
#6
executeBatch
#7
forward
#9
0x6a742334
#10
setData
#4
0x5acec890
#5
0x0f6795d9
· blocks 1
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78eb19eb…6131
0x34b655…2a6f
4 touches
1 conflict
0x99c5409a…25b7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x5cc231f5…f1cd
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
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
0x78eb19ebdb…c76131
Audit this contract →
← previous block
·
next block →
recent activity