← previous blocknext block →recent activity
Analyzing
Block #76,091,053
23 transactions · 18 stateful · 2026-05-21 17:36:46 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,091,053 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w012w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x962a2ed5…e4fb
0x065c9d…c394
4 touches
1 conflict
0x1c97d8d6…e4d2
0xd32edf…ff58
3 touches
1 conflict
0x06e40499…165e
0x1d1325…2305
2 touches
0 conflicts
0x1b60b708…5b4b
0x1d1325…2305
2 touches
0 conflicts
0x24781048…4772
0x2a68ba…90c5
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
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity