pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,274,803
← previous block
next block →
recent activity
Analyzing
Block #99,274,803
9 transactions · 9 stateful · 2026-08-26 07:56:00 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,274,803
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
0x59558d29
#4
transferWithAuthorization
· blocks 1
#6
0x6a8e9c88
#7
setData
#2
0x5acec890
· blocks 1
#5
transferWithAuthorization
#8
execOrders
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
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9df82d7…549f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x1ecde9da…3735
0x34b655…2a6f
2 touches
0 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
2 touches
0 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
2 touches
0 conflicts
0x71fad9ce…c11f
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
1 conflict on slot
0xd9df82d7e2…4b549f
Audit this contract →
← previous block
·
next block →
recent activity