pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,845,898
← previous block
next block →
recent activity
Analyzing
Block #93,845,898
9 transactions · 9 stateful · 2026-08-07 06:16:29 UTC
Parallelism
67
/100
Blocked
44
%
Avg conflicts / tx
0.56
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,845,898
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 4
#5
updateDataFeedsValuesPartial
#7
0x6a7578b5
#8
setData
#2
0x5acec890
· blocks 1
#4
0x0f6795d9
#6
0x0f6795d9
#3
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0x2fd12b6c…02cc
0x34b655…2a6f
2 touches
0 conflicts
0x4477eee6…7c43
0x34b655…2a6f
2 touches
0 conflicts
0x45d87399…4382
0x34b655…2a6f
2 touches
0 conflicts
0x47a3d808…bf46
0x34b655…2a6f
2 touches
0 conflicts
0x4d4389b2…6e07
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
3 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity