← previous blocknext block →recent activity
Analyzing
Block #74,762,238
14 transactions · 11 stateful · 2026-05-15 13:40:03 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,762,238 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa26cc52f…603a
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x388e001a…7e04
0x34b655…2a6f
4 touches
1 conflict
0x150af51d…9c42
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x414e9446…4b59
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 0xa26cc52fff…b3603a
Audit this contract →
← previous block·next block →recent activity