← previous blocknext block →recent activity
Analyzing
Block #76,090,800
17 transactions · 13 stateful · 2026-05-21 17:35:05 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,090,800 · 17 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
5w06w07w18w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xaa47606d…91cb
0x9f3832…4ae4
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x69cd5c19…88ca
0x9f3832…4ae4
4 touches
1 conflict
0xaa47606d…91ca
0x9f3832…4ae4
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
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: 0x9f383273…514ae4
1 conflict on slot 0x7cf5136feb…2fba69
Audit this contract →
← previous block·next block →recent activity