pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,842,907
← previous block
next block →
recent activity
Analyzing
Block #98,842,907
10 transactions · 8 stateful · 2026-08-24 19:36:18 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,842,907
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
· blocks 1
#3
0x59558d29
#4
0x6a8c9daa
#5
setData
#6
0x2d7aa9…25b0
#7
execOrders
· blocks 2
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x556beb43…e627
0x34b655…2a6f
2 touches
0 conflicts
0x74cdc294…26a8
0x34b655…2a6f
2 touches
0 conflicts
0x75f36d60…8556
0x34b655…2a6f
2 touches
0 conflicts
0x7aa463de…e7b8
0x34b655…2a6f
2 touches
0 conflicts
0x93b40733…be1e
0x34b655…2a6f
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity