← previous blocknext block →recent activity
Analyzing
Block #73,374,524
13 transactions · 11 stateful · 2026-05-09 03:16:22 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,374,524 · 13 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfadb0d6a…e64d
0x34b655…2a6f
4 touches
1 conflict
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0x4de9456e…7dac
0x065c9d…c394
2 touches
0 conflicts
0x5756f106…e33d
0x065c9d…c394
2 touches
0 conflicts
0x5aebb1e6…5743
0x065c9d…c394
2 touches
0 conflicts
0x72f7ffce…8cd0
0x065c9d…c394
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 0xfadb0d6a7a…b4e64d
Audit this contract →
← previous block·next block →recent activity