pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,441,189
← previous block
next block →
recent activity
Analyzing
Block #107,441,189
13 transactions · 12 stateful · 2026-09-23 22:32:10 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,441,189
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0x59558d29
#4
0x928e4afa
· blocks 1
#6
execPerpOps
#7
execPerpOps
#8
forward
#9
relay
#10
0x6ab4536d
#11
setData
#12
execOrders
#2
matchOrders
#5
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd85c966d…f345
0x99c7a7…8bf0
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x56f91464…1e91
0x37db7f…ec7b
4 touches
1 conflict
0x640481cc…a2df
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1b0
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1b1
0x37db7f…ec7b
4 touches
1 conflict
0x040740a5…29f6
0x754704…b603
4 touches
1 conflict
0x1004cdd3…ee46
0x754704…b603
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:
0x99c7a72e…c78bf0
1 conflict on slot
0xd85c966d06…3ef345
Audit this contract →
← previous block
·
next block →
recent activity