pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,232,205
10 transactions · 7 stateful · 2026-05-17 17:58:25 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,232,205 · 10 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x29530319…bb27
0x1efe02…37d6
2 touches
0 conflicts
0x754493a0…e69b
0x3bd359…433a
2 touches
0 conflicts
0x7332125a…5518
0x91b81b…6d56
2 touches
0 conflicts
0x1005f9aa…8bfc
0xea1b8e…c5ec
2 touches
0 conflicts
0x1005f9aa…8bfe
0xea1b8e…c5ec
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: 0xfd44b351…7f00d1
1 conflict on slot 0x00bac0131a…bba28c
Audit this contract →
← previous block·next block →recent activity