← previous blocknext block →recent activity
Analyzing
Block #75,478,324
65 transactions · 18 stateful · 2026-05-18 21:23:45 UTC
Parallelism
94/100
Blocked
33%
Avg conflicts / tx
0.14
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,478,324 · 65 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
24w025w036w147w152w053w161w162w263w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0004
0x9b60e5…f8ac
4 touches
1 conflict
0xee0a9ebb…c425
0x0555e3…2b9c
4 touches
1 conflict
0xe1e41849…9772
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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
6 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity