pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,574,104
← previous block
next block →
recent activity
Analyzing
Block #108,574,104
12 transactions · 11 stateful · 2026-09-27 21:36:31 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
#108,574,104
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9ac0761c
· blocks 1
#3
0x26c66755
#4
0x59558d29
#5
0xa96df62f
#6
0xab083028
#7
0xa96df62f
#8
0x41a8f47c
#9
execFwdPositionOpsV2
#10
forward
#11
setData
#2
0x9ac0761c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4aa8b305…4ace
0x860869…ff01
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x4b6e74b5…ea21
0x01bff4…1071
2 touches
0 conflicts
0xcce63cfd…50fe
0x01bff4…1071
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0002
0x1fb37a…a010
2 touches
0 conflicts
0x00000000…0003
0x1fb37a…a010
2 touches
0 conflicts
0x00000000…0005
0x1fb37a…a010
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:
0x8608690f…c8ff01
1 conflict on slot
0x4aa8b3059e…9d4ace
Audit this contract →
← previous block
·
next block →
recent activity