← previous blocknext block →recent activity
Analyzing
Block #76,213,200
14 transactions · 12 stateful · 2026-05-22 07:10:03 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,213,200 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2489767e…f3e3
0x065c9d…c394
2 touches
0 conflicts
0x4d429d70…08f2
0x065c9d…c394
2 touches
0 conflicts
0x68ef0424…3434
0x065c9d…c394
2 touches
0 conflicts
0xbae465ac…5245
0x065c9d…c394
2 touches
0 conflicts
0xc5e499f1…e852
0x065c9d…c394
2 touches
0 conflicts
0xd498adc1…868b
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
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity