pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,128,855
← previous block
next block →
recent activity
Analyzing
Block #95,128,855
12 transactions · 11 stateful · 2026-08-11 18:07:57 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,128,855
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x0f6795d9
#3
0x0f6795d9
#4
0x3f5c179b
#5
executeBatch
· blocks 1
#7
0x0f6795d9
#8
updateDataFeedsValuesPartial
#9
0x6a7b6575
#10
increaseAllowance
#11
setData
#6
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x785f8831…2fb1
0xe52b14…7230
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x15c37eee…5855
0x34b655…2a6f
2 touches
0 conflicts
0x2d1df17e…b68c
0x34b655…2a6f
2 touches
0 conflicts
0x3c0a486b…c128
0x34b655…2a6f
2 touches
0 conflicts
0x45e9e6f3…fe07
0x34b655…2a6f
2 touches
0 conflicts
0x48b13e5e…3c2a
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:
0xe52b1424…bb7230
1 conflict on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity