← previous blocknext block →recent activity
Analyzing
Block #73,214,073
28 transactions · 17 stateful · 2026-05-08 09:28:54 UTC
Parallelism
86/100
Blocked
47%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,214,073 · 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
4w013w014w117w219w120w221w322w123w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdaca243a…f9de
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0xbf6827d3…fdb5
0x065c9d…c394
4 touches
1 conflict
0x09526425…9729
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x4582e32d…1abe
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 0xdaca243a5e…09f9de
Audit this contract →
← previous block·next block →recent activity