← previous blocknext block →recent activity
Analyzing
Block #74,766,518
26 transactions · 18 stateful · 2026-05-15 14:08:43 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,766,518 · 26 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
1w02w14w25w06w07w112w019w122w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x8404070b…464d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x3914b736…9377
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
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 0xb9868b5233…c6c77f
Audit this contract →
← previous block·next block →recent activity