← previous blocknext block →recent activity
Analyzing
Block #76,197,253
19 transactions · 14 stateful · 2026-05-22 05:24:00 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,197,253 · 19 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
1w06w17w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xb3870dbe…bef3
0x2a68ba…90c5
4 touches
1 conflict
0x4796b982…3394
0x065c9d…c394
2 touches
0 conflicts
0x5e1ce365…3f2e
0x065c9d…c394
2 touches
0 conflicts
0x74803a68…431c
0x065c9d…c394
2 touches
0 conflicts
0x76733a19…f819
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
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
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity