pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,678,976
← previous block
next block →
recent activity
Analyzing
Block #98,678,976
12 transactions · 11 stateful · 2026-08-24 05:48:05 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,678,976
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
0x5acec890
#4
0x59558d29
#5
0x94defb17
· blocks 1
#7
execOrders
#8
0x6a8bdb8c
#9
setData
#10
execOrders
· blocks 1
#6
0x94defb17
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0fa05bb…dda8
0x8964d7…10f8
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xa4a8346a…6981
0x8964d7…10f8
4 touches
1 conflict
0xa4a8346a…6982
0x8964d7…10f8
4 touches
1 conflict
0xa4a8346a…6984
0x8964d7…10f8
4 touches
1 conflict
0xe0fa05bb…dda1
0x8964d7…10f8
4 touches
1 conflict
0xe0fa05bb…dda2
0x8964d7…10f8
4 touches
1 conflict
0xe0fa05bb…dda5
0x8964d7…10f8
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:
0x8964d7c9…5b10f8
1 conflict on slot
0xe0fa05bb95…dedda8
Audit this contract →
← previous block
·
next block →
recent activity