pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,681,549
← previous block
next block →
recent activity
Analyzing
Block #90,681,549
11 transactions · 10 stateful · 2026-07-27 04:54:53 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,681,549
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
executeBatch
· blocks 1
#4
execFwdPositionOps
#5
handleOps
#6
execOrder
#7
setData
#8
execOrders
· blocks 1
#9
execOrders
#3
executeBatch
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xee8defd7…73c4
0xe52b14…7230
4 touches
1 conflict
0xef7c06bc…c2eb
0xe52b14…7230
4 touches
1 conflict
0x59eabcdc…e01d
0x34b655…2a6f
4 touches
1 conflict
0x6b436af2…3c05
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x09e0690d…6e3d
0xe52b14…7230
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:
0xe52b1424…bb7230
1 conflict on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity