← previous blocknext block →recent activity
Analyzing
Block #74,772,942
16 transactions · 14 stateful · 2026-05-15 14:51:45 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,772,942 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x45b9e08c…a11b
0x34b655…2a6f
6 touches
3 conflicts
0x36cdae67…8407
0x34b655…2a6f
6 touches
3 conflicts
0x5aeaf08b…cbf7
0x34b655…2a6f
6 touches
3 conflicts
0x7b97d40a…09ed
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 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity