← previous blocknext block →recent activity
Analyzing
Block #76,441,653
13 transactions · 11 stateful · 2026-05-23 08:31:30 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,441,653 · 13 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
2w03w05w16w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65ef6e8c…d10d
0xa6afd3…d132
6 touches
3 conflicts
0xda693078…02d1
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd5bfc8fb…071f
0x2a68ba…90c5
2 touches
0 conflicts
0x247d3d81…6084
0x2c4667…b389
2 touches
0 conflicts
0x5ee3dd55…bf82
0x2c4667…b389
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: 0xa6afd386…b0d132
3 conflicts on slot 0x65ef6e8c80…e2d10d
Audit this contract →
← previous block·next block →recent activity