pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,199,366
← previous block
next block →
recent activity
Analyzing
Block #75,199,366
11 transactions · 9 stateful · 2026-05-17 14:19:08 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,199,366
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x0f6795d9
#7
forward
#8
0x6df9e92b
· blocks 1
#10
setData
#2
0x1ffa3c9b
#9
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x2e2214a9…fe0d
0x5d823e…89c6
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x5d823e…89c6
4 touches
1 conflict
0x50997ada…364d
0x5d823e…89c6
4 touches
1 conflict
0x6b319071…a105
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0000
0xfdc9ea…8789
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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:
0xfdc9ea59…b68789
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity