← previous blocknext block →recent activity
Analyzing
Block #74,891,586
29 transactions · 22 stateful · 2026-05-16 04:03:17 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,891,586 · 29 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
1w02w19w111w012w114w015w016w117w219w323w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc6ea79…e2dc
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x88e1039d…f8ae
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x9efa6cc5…7be4
0xd32edf…ff58
5 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 0x9fc6ea791d…ace2dc
Audit this contract →
← previous block·next block →recent activity