← previous blocknext block →recent activity
Analyzing
Block #75,844,959
22 transactions · 15 stateful · 2026-05-20 14:16:54 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,844,959 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w110w011w112w213w314w416w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a7
0x8d66a4…3095
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb8
0x1b6862…e19c
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x32b2548c…4105
0x34b655…2a6f
4 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity