pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#109,143,669
← previous block
next block →
recent activity
Analyzing
Block #109,143,669
10 transactions · 8 stateful · 2026-09-29 21:30:22 UTC
Parallelism
70
/100
Blocked
38
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#109,143,669
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
executeBatch
· blocks 2
#4
forward
#5
0xed82b078
#6
0xed82b078
#7
setData
#8
execOrders
· blocks 1
#2
executeBatch
· blocks 1
#9
execOrders
#3
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x58733c38…f2cd
0xe52b14…7230
4 touches
1 conflict
0x693b762e…1fcd
0xe52b14…7230
4 touches
1 conflict
0x6a3749da…c493
0xe52b14…7230
4 touches
1 conflict
0x6ad5feb6…5606
0xe52b14…7230
4 touches
1 conflict
0xc4a2f619…eb38
0xe52b14…7230
4 touches
1 conflict
0xd4e69a1d…6139
0xe52b14…7230
4 touches
1 conflict
0xee8defd7…73c4
0xe52b14…7230
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:
0xe52b1424…bb7230
3 conflicts on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity