← previous blocknext block →recent activity
Analyzing
Block #76,437,823
14 transactions · 14 stateful · 2026-05-23 08:05:58 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,437,823 · 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
2w03w14w05w06w19w211w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x309ef367…e8a1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x35a3ef5e…b62e
0x34b655…2a6f
6 touches
3 conflicts
0xc2e147bc…8b24
0xd32edf…ff58
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0x309ef36779…d6e8a1
Audit this contract →
← previous block·next block →recent activity