pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,334,168
14 transactions · 13 stateful · 2026-05-13 14:00:37 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,334,168 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x62d080e9…4a7c
0x34b655…2a6f
4 touches
1 conflict
0x8db1e0f2…2fcf
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0x99f080dc…58c1
0x34b655…2a6f
4 touches
1 conflict
0x9be2b99a…a959
0x34b655…2a6f
4 touches
1 conflict
0xd6e02140…b2b5
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: 0xc8689a47…62ee79
1 conflict on slot 0xc6417de023…802191
Audit this contract →
← previous block·next block →recent activity