← previous blocknext block →recent activity
Analyzing
Block #73,807,490
9 transactions · 9 stateful · 2026-05-11 03:33:27 UTC
Parallelism
44/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,807,490 · 9 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
8 touches
6 conflicts
0x5d70606a…1d53
0x34b655…2a6f
8 touches
6 conflicts
0x129ba946…48ab
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
6 touches
3 conflicts
0x0fa5e7bf…a4da
0x34b655…2a6f
6 touches
3 conflicts
0x57de3828…3fbb
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity