pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,457,037
21 transactions · 13 stateful · 2026-05-14 03:38:24 UTC
Parallelism
90/100
Blocked
23%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,457,037 · 21 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
1w03w19w010w012w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00a7
0xbb4738…ed6c
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x969c3d70…4604
0x34b655…2a6f
4 touches
1 conflict
0xef17b8cd…9511
0x34b655…2a6f
4 touches
1 conflict
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0xbdd29ea9…58be
0xad96c3…8d7c
4 touches
1 conflict
0xf49d1e10…0563
0xbb4738…ed6c
3 touches
1 conflict
0x91ff71ac…7de5
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: 0xbb4738d0…eeed6c
1 conflict on slot 0x0000000000…0000a7
Audit this contract →
← previous block·next block →recent activity