pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,759,741
← previous block
next block →
recent activity
Analyzing
Block #92,759,741
8 transactions · 6 stateful · 2026-08-03 11:13:05 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,759,741
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x94defb17
#2
0x0f6795d9
· blocks 1
#4
0x6a707839
#5
setData
#6
withdraw
#7
0x59558d29
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06ab8d8…3589
0x34b655…2a6f
4 touches
1 conflict
0x4c04ce68…d007
0x34b655…2a6f
4 touches
1 conflict
0x29f027f1…1649
0x34b655…2a6f
2 touches
0 conflicts
0x2f93d1d7…914a
0x34b655…2a6f
2 touches
0 conflicts
0x3215d103…515a
0x34b655…2a6f
2 touches
0 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
2 touches
0 conflicts
0x54f22684…1b61
0x34b655…2a6f
2 touches
0 conflicts
0x177211e2…1c2d
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
0xf06ab8d81b…9b3589
Audit this contract →
← previous block
·
next block →
recent activity