← previous blocknext block →recent activity
Analyzing
Block #73,818,997
25 transactions · 17 stateful · 2026-05-11 04:50:01 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,818,997 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w08w110w211w012w113w214w315w220w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x0e8a2bd3…ef4c
0x34b655…2a6f
6 touches
3 conflicts
0x23951077…539b
0x34b655…2a6f
6 touches
3 conflicts
0x2d975111…5f52
0x34b655…2a6f
6 touches
3 conflicts
0x313f2565…5b00
0x34b655…2a6f
6 touches
3 conflicts
0x3638e1ad…ec0e
0x34b655…2a6f
6 touches
3 conflicts
0x57de3828…3fbb
0x34b655…2a6f
6 touches
3 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: Perpl
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity