← previous blocknext block →recent activity
Analyzing
Block #74,949,356
19 transactions · 16 stateful · 2026-05-16 10:29:05 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,949,356 · 19 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
1w02w16w07w18w29w310w411w516w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x29776324…c0ea
0x34b655…2a6f
4 touches
1 conflict
0x34f7d9f7…019b
0x34b655…2a6f
4 touches
1 conflict
0x422efe37…5ac3
0x34b655…2a6f
4 touches
1 conflict
0x475d29e4…3caf
0x34b655…2a6f
4 touches
1 conflict
0x49f69157…4445
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
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
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity