pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,783,222
← previous block
next block →
recent activity
Analyzing
Block #75,783,222
10 transactions · 7 stateful · 2026-05-20 07:24:40 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,783,222
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x15ea9545
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0xce1e7030
#7
0x5339c59f
#8
setData
#9
0x5f9021…0563
#3
0xe2dc7dc3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0x9560013d…8caf
0x91b81b…6d56
4 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
4 touches
1 conflict
0xa5bbce14…e473
0xea1b8e…c5ec
4 touches
1 conflict
0xa5bbce14…e474
0xea1b8e…c5ec
4 touches
1 conflict
0xbc33a929…8b24
0xea1b8e…c5ec
4 touches
1 conflict
0xd8eb2d31…2ac0
0xea1b8e…c5ec
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:
LeverUp: LeverUp
1 conflict on slot
0xeef70cb93b…ad5de7
Audit this contract →
← previous block
·
next block →
recent activity