pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,743,057
← previous block
next block →
recent activity
Analyzing
Block #98,743,057
11 transactions · 10 stateful · 2026-08-24 11:13:36 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,743,057
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x6ad2e98b
#3
0xab083028
#4
execOrder
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0x6a8c27d8
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a2cd1ed…9eba
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbff3a360…6ae5
0x34b655…2a6f
4 touches
1 conflict
0xb42343e0…2a28
0x34b655…2a6f
3 touches
1 conflict
0x7aa91b8f…d070
0x2b46c0…1669
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
0x9a2cd1ed33…9d9eba
Audit this contract →
← previous block
·
next block →
recent activity