pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,673,674
11 transactions · 9 stateful · 2026-05-10 12:30:51 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,673,674 · 11 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe75ce681…ba60
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0dbf9688…c6cf
0xd18b7e…414b
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xd2e87a61…c15d
0xd32edf…ff58
3 touches
1 conflict
0x0b8390ef…5a78
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: 0x188d586d…f9ea8e
1 conflict on slot 0xe75ce68176…09ba60
Audit this contract →
← previous block·next block →recent activity