pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#109,229,308
← previous block
next block →
recent activity
Analyzing
Block #109,229,308
10 transactions · 8 stateful · 2026-09-30 04:41:31 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#109,229,308
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
0x61d59c2d
· blocks 1
#4
0xab083028
#5
0x5acec890
#6
0x3f5c179b
#7
0xed82b078
#8
0x57368ddf
#9
execute
#3
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4d8e8…ffa8
0x508254…98bd
4 touches
1 conflict
0x4ea2b33b…7dbc
0x508254…98bd
4 touches
1 conflict
0xd23e9468…042c
0x508254…98bd
4 touches
1 conflict
0xd23e9468…0438
0x508254…98bd
4 touches
1 conflict
0xd23e9468…0454
0x508254…98bd
4 touches
1 conflict
0xd23e9468…045c
0x508254…98bd
4 touches
1 conflict
0xd23e9468…0463
0x508254…98bd
4 touches
1 conflict
0xd23e9468…049a
0x508254…98bd
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:
0x508254c8…4a98bd
1 conflict on slot
0xe1c4d8e8bd…deffa8
Audit this contract →
← previous block
·
next block →
recent activity