pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,512,111
← previous block
next block →
recent activity
Analyzing
Block #93,512,111
12 transactions · 10 stateful · 2026-08-06 02:18:28 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,512,111
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
#3
updatePriceFeedsIfNecessary
#4
0x94defb17
· blocks 2
#7
0xb5d78142
#8
closeBetting
#9
setData
#10
0x39435dac
#11
0x59558d29
#5
0x94defb17
· blocks 1
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de4928f…173a
0x968279…9342
6 touches
3 conflicts
0x5de4928f…173b
0x968279…9342
6 touches
3 conflicts
0x5de4928f…173d
0x968279…9342
6 touches
3 conflicts
0x840ec797…7bc3
0x968279…9342
6 touches
3 conflicts
0x840ec797…7bc4
0x968279…9342
6 touches
3 conflicts
0x840ec797…7bc7
0x968279…9342
6 touches
3 conflicts
0x840ec797…7bc8
0x968279…9342
6 touches
3 conflicts
0x840ec797…7bc9
0x968279…9342
6 touches
3 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:
0x96827978…f09342
3 conflicts on slot
0x5de4928f02…bd173a
Audit this contract →
← previous block
·
next block →
recent activity