pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,862,023
← previous block
next block →
recent activity
Analyzing
Block #94,862,023
11 transactions · 10 stateful · 2026-08-10 19:45:01 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,862,023
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
0x5acec890
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#7
handleOps
#8
createGameByAdmin
#9
setData
#10
0x59558d29
#3
0x5acec890
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66707c66…4d37
0x34b655…2a6f
4 touches
1 conflict
0x0227484c…b688
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
0x34b655…2a6f
4 touches
1 conflict
0xa4dae615…1cf8
0x34b655…2a6f
4 touches
1 conflict
0xb9a63bff…00e4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
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
0x66707c66ce…f74d37
Audit this contract →
← previous block
·
next block →
recent activity