pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,280,102
← previous block
next block →
recent activity
Analyzing
Block #93,280,102
8 transactions · 7 stateful · 2026-08-05 06:52:01 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,280,102
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
0xee83e0a5
#6
0x8b80a919
#7
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc8ba2b5…e2d1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x417b3755…ffe9
0x34b655…2a6f
4 touches
1 conflict
0x4342a5b9…c37d
0x34b655…2a6f
4 touches
1 conflict
0x8f888556…f387
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc8c615d4…5da3
0x34b655…2a6f
4 touches
1 conflict
0x1e9bb30c…e78e
0x34b655…2a6f
3 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:
Perpl
1 conflict on slot
0xfc8ba2b5c8…73e2d1
Audit this contract →
← previous block
·
next block →
recent activity