← previous blocknext block →recent activity
Analyzing
Block #76,431,536
8 transactions · 6 stateful · 2026-05-23 07:24:06 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,431,536 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc906436c…b676
0xa6afd3…d132
4 touches
1 conflict
0xf0d3c3f0…c09e
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0xd5bfc8fb…071f
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x619c99af…ca51
0x8d9f8e…050c
2 touches
0 conflicts
0x251b9027…5a32
0xa6afd3…d132
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
1 conflict on slot 0xc906436ccb…23b676
Audit this contract →
← previous block·next block →recent activity