← previous blocknext block →recent activity
Analyzing
Block #73,749,240
28 transactions · 13 stateful · 2026-05-10 21:00:48 UTC
Parallelism
86/100
Blocked
54%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,749,240 · 28 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
6w07w113w014w115w216w324w025w126w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ad
0x8d66a4…3095
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0x9dc9fa5f…7f23
0x34b655…2a6f
4 touches
1 conflict
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xe8a35d5a…cb9d
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity