← previous blocknext block →recent activity
Analyzing
Block #75,944,403
18 transactions · 17 stateful · 2026-05-21 01:19:38 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,944,403 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w59w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x08d31c28…d50f
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x8fa0889f…0346
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x5e91408d…0e18
0x065c9d…c394
2 touches
0 conflicts
0xcb898fa2…da97
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: 0xab35264b…1cfa38
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity