← previous blocknext block →recent activity
Analyzing
Block #75,531,965
24 transactions · 20 stateful · 2026-05-19 03:30:03 UTC
Parallelism
75/100
Blocked
70%
Avg conflicts / tx
1.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,531,965 · 24 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
1w02w14w05w26w37w18w09w110w211w312w413w515w316w421w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd6a7469a…4fe8
0x34b655…2a6f
8 touches
6 conflicts
0x5086c64a…28ba
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
8 touches
6 conflicts
0x8a35acfb…d1aa
0x8d66a4…3095
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
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
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity