pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,619,044
← previous block
next block →
recent activity
Analyzing
Block #108,619,044
11 transactions · 10 stateful · 2026-09-28 01:22:46 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,619,044
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3e2e8792
#2
execPerpOps
#3
execPerpOps
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
executeBatch
#7
0x3f5c179b
#8
0x84403c1b
· blocks 1
#10
setData
#9
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c3e6e76…43c3
0x34b655…2a6f
4 touches
1 conflict
0xcd0e79e1…4c56
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0x66fc0764…05fd
0x34b655…2a6f
2 touches
0 conflicts
0x945843e4…a3cd
0x34b655…2a6f
2 touches
0 conflicts
0xba1edffb…323e
0x34b655…2a6f
2 touches
0 conflicts
0xca841faa…486a
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
1 conflict on slot
0x3c3e6e76fa…de43c3
Audit this contract →
← previous block
·
next block →
recent activity