pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,229,541
← previous block
next block →
recent activity
Analyzing
Block #93,229,541
10 transactions · 9 stateful · 2026-08-05 02:37:48 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,229,541
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#5
0x0f6795d9
#6
setData
#7
0x39435dac
· blocks 1
#9
0xc7e3ec2c
#4
0x3f5c179b
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x086f580e…090c
0x851145…3f07
4 touches
1 conflict
0xabc6fb06…1401
0x851145…3f07
4 touches
1 conflict
0x93b10504…587d
0x851145…3f07
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x74137b07…5880
0x34b655…2a6f
4 touches
1 conflict
0x7a2fc410…c088
0x34b655…2a6f
4 touches
1 conflict
0x7da6eb60…b34e
0x34b655…2a6f
4 touches
1 conflict
0x8d60e997…eaa2
0x34b655…2a6f
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:
0x851145ea…9f3f07
1 conflict on slot
0x086f580e19…03090c
Audit this contract →
← previous block
·
next block →
recent activity