← previous blocknext block →recent activity
Analyzing
Block #76,237,100
23 transactions · 21 stateful · 2026-05-22 09:49:39 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,237,100 · 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
2w04w15w06w27w18w19w010w111w212w314w015w016w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x00000000…0001
0xbab229…9388
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe4606ee6…52fa
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity