pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,664,249
← previous block
next block →
recent activity
Analyzing
Block #108,664,249
11 transactions · 9 stateful · 2026-09-28 05:10:26 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,664,249
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0x5acec890
#4
0x5acec890
#5
updatePrices
#6
0x000000b2
#7
0x84403c1b
· blocks 1
#9
setData
#10
0x000000b2
#2
0xab083028
#8
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2870700…9dd7
0x34b655…2a6f
4 touches
1 conflict
0xe92bc5fd…81e3
0x34b655…2a6f
4 touches
1 conflict
0xf3b3a6e9…8cd2
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1ad8153e…06bf
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x941bd594…21fd
0x34b655…2a6f
2 touches
0 conflicts
0xe098738f…9bbe
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
0xe28707007a…689dd7
Audit this contract →
← previous block
·
next block →
recent activity