← previous blocknext block →recent activity
Analyzing
Block #75,919,707
7 transactions · 6 stateful · 2026-05-20 22:35:14 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,919,707 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10f5f4d8…572e
0x34b655…2a6f
4 touches
1 conflict
0x280638c7…c3ff
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a5
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a6
0x8d66a4…3095
4 touches
1 conflict
0xc009105d…96f7
0x8d66a4…3095
4 touches
1 conflict
0x5e965837…7eb3
0x065c9d…c394
2 touches
0 conflicts
0x650d3296…ea6d
0x065c9d…c394
2 touches
0 conflicts
0xd2eda5b5…35ce
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0x10f5f4d8d3…cc572e
Audit this contract →
← previous block·next block →recent activity