pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,598,886
12 transactions · 11 stateful · 2026-05-14 19:29:28 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,598,886 · 12 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
1w02w15w06w17w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x3c85da13…3846
0x065c9d…c394
4 touches
1 conflict
0x5417712f…101a
0x065c9d…c394
3 touches
1 conflict
0xed56e4da…baa5
0x065c9d…c394
3 touches
1 conflict
0xc24e2f7a…0ac0
0x065c9d…c394
3 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: 0x065c9d28…a9c394
1 conflict on slot 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity