← previous blocknext block →recent activity
Analyzing
Block #73,037,975
21 transactions · 16 stateful · 2026-05-07 13:57:16 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,037,975 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w210w011w112w213w314w415w119w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdaca243a…f9de
0x34b655…2a6f
12 touches
15 conflicts
0x3702b140…97ea
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x35b65947…44d1
0xc8689a…ee79
8 touches
6 conflicts
0x005fb969…2d97
0x34b655…2a6f
8 touches
6 conflicts
0x085df2c1…305a
0x34b655…2a6f
8 touches
6 conflicts
0x3c35979a…975d
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xdaca243a5e…09f9de
Audit this contract →
← previous block·next block →recent activity