← previous blocknext block →recent activity
Analyzing
Block #75,337,262
23 transactions · 18 stateful · 2026-05-18 05:41:23 UTC
Parallelism
87/100
Blocked
39%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,337,262 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w110w011w112w015w116w017w121w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x019883…2a9a
4 touches
1 conflict
0x00000000…0002
0x019883…2a9a
4 touches
1 conflict
0x44ad89ba…cf83
0x0cc9b2…7777
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb85
0x1b6862…e19c
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
3 conflicts on slot 0x676f9f01ee…dea8ac
Audit this contract →
← previous block·next block →recent activity