← previous blocknext block →recent activity
Analyzing
Block #73,399,008
11 transactions · 11 stateful · 2026-05-09 05:59:21 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,399,008 · 11 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
3w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedb848fe…6534
0x34b655…2a6f
8 touches
6 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
8 touches
6 conflicts
0xfadb0d6a…e64d
0x34b655…2a6f
8 touches
6 conflicts
0x273d80cd…9ecc
0x34b655…2a6f
6 touches
3 conflicts
0x908d4442…2c4b
0x34b655…2a6f
6 touches
3 conflicts
0xc6417de0…2191
0xc8689a…ee79
6 touches
3 conflicts
0xd49762c9…1359
0x34b655…2a6f
6 touches
3 conflicts
0x6eba5e7f…4b52
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 0xedb848fed2…6e6534
Audit this contract →
← previous block·next block →recent activity