pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,988,764
← previous block
next block →
recent activity
Analyzing
Block #108,988,764
10 transactions · 5 stateful · 2026-09-29 08:28:47 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,988,764
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x59558d29
#3
0x84403c1b
#4
0x84403c1b
#5
0x84403c1b
#6
0x1ea3e879
· blocks 1
#8
0xed82b078
#9
setData
#7
0x1ea3e879
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x034f4886…f7e3
0x6f6493…b480
4 touches
1 conflict
0x09084072…9ea3
0x6f6493…b480
4 touches
1 conflict
0x0e9c0440…d2d0
0x6f6493…b480
4 touches
1 conflict
0x2117902d…c330
0x6f6493…b480
4 touches
1 conflict
0x438bdcd1…2279
0x6f6493…b480
4 touches
1 conflict
0x4392b446…81d8
0x6f6493…b480
4 touches
1 conflict
0x4567727c…3301
0x6f6493…b480
4 touches
1 conflict
0x46ab5410…9dd7
0x6f6493…b480
4 touches
1 conflict
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:
0x6f6493e3…08b480
1 conflict on slot
0x034f4886af…1ef7e3
Audit this contract →
← previous block
·
next block →
recent activity