← previous blocknext block →recent activity
Analyzing
Block #74,572,050
8 transactions · 8 stateful · 2026-05-14 16:29:54 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,572,050 · 8 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
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x037849a8…fa88
0x34b655…2a6f
2 touches
0 conflicts
0x037849a8…fa8d
0x34b655…2a6f
2 touches
0 conflicts
0x257251ca…49b8
0x34b655…2a6f
2 touches
0 conflicts
0x6c44331f…9735
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
3 conflicts on slot 0x23a320fbfb…26cbd7
Audit this contract →
← previous block·next block →recent activity