pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,845,940
← previous block
next block →
recent activity
Analyzing
Block #73,845,940
9 transactions · 8 stateful · 2026-05-11 07:49:19 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,845,940
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x98717539
· blocks 2
#5
updateDataFeedsValuesPartial
#6
setData
#7
updateTemporalNumericValuesV1
#4
0x98717539
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8240d70c…7c3b
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x3702b140…97ea
0x34b655…2a6f
2 touches
0 conflicts
0x3d93727e…c307
0x34b655…2a6f
2 touches
0 conflicts
0x401be839…8ac0
0x34b655…2a6f
2 touches
0 conflicts
0x65e795ca…0320
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x8240d70c8a…f27c3b
Audit this contract →
← previous block
·
next block →
recent activity