pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,333,221
← previous block
next block →
recent activity
Analyzing
Block #74,333,221
8 transactions · 6 stateful · 2026-05-13 13:54:18 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,333,221
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updateDataFeedsValuesPartial
#3
0x1a945f9c
· blocks 1
#5
0x6a048301
#6
setData
#7
0x33dce5…63f6
#4
0x366fe5db
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x5f47b4ad…567c
0x1efe02…37d6
2 touches
0 conflicts
0xa3c9a7af…d146
0x1efe02…37d6
2 touches
0 conflicts
0xf123b3fb…7bfb
0x1efe02…37d6
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:
LeverUp: LeverUp
1 conflict on slot
0xb6b74ae0ff…d48d5e
Audit this contract →
← previous block
·
next block →
recent activity