← previous blocknext block →recent activity
Analyzing
Block #75,516,443
18 transactions · 8 stateful · 2026-05-19 01:45:11 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,516,443 · 18 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a8
0x8d66a4…3095
3 touches
1 conflict
0xcc6521c1…c892
0x8d66a4…3095
3 touches
1 conflict
0x19c959f1…5341
0x065c9d…c394
2 touches
0 conflicts
0x362c52e4…7b17
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity