← previous blocknext block →recent activity
Analyzing
Block #73,688,470
8 transactions · 8 stateful · 2026-05-10 14:10:45 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,688,470 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd49762c9…1359
0x34b655…2a6f
4 touches
1 conflict
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x2a4146fa…ab95
0x34b655…2a6f
4 touches
1 conflict
0xd0a6cde5…29cc
0x34b655…2a6f
4 touches
1 conflict
0x3638e1ad…ec0e
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
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: Perpl
1 conflict on slot 0xd49762c96f…3b1359
Audit this contract →
← previous block·next block →recent activity