← previous blocknext block →recent activity
Analyzing
Block #74,477,023
7 transactions · 7 stateful · 2026-05-14 05:51:18 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,477,023 · 7 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
1w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa486f342…64d5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x4582e32d…1abe
0x34b655…2a6f
2 touches
0 conflicts
0x543da691…8f99
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x8b8e4020…11b0
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
1 conflict on slot 0xa486f34281…4664d5
Audit this contract →
← previous block·next block →recent activity