← previous blocknext block →recent activity
Analyzing
Block #75,847,212
18 transactions · 14 stateful · 2026-05-20 14:32:00 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,847,212 · 18 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
1w02w15w06w17w28w313w015w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0335ae80…8414
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1a4
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d19f
0x8d66a4…3095
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x2ce2d49e…d18c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x6dedaff6…161b
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: 0x8d66a43f…113095
3 conflicts on slot 0x0335ae8037…c18414
Audit this contract →
← previous block·next block →recent activity