← previous blocknext block →recent activity
Analyzing
Block #76,436,328
17 transactions · 15 stateful · 2026-05-23 07:56:00 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,436,328 · 17 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
1w02w04w15w06w07w18w110w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65ef6e8c…d10d
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe63e4686…4596
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xda693078…02d1
0xa6afd3…d132
4 touches
1 conflict
0x3c862df0…b577
0x34b655…2a6f
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: 0xa6afd386…b0d132
3 conflicts on slot 0x65ef6e8c80…e2d10d
Audit this contract →
← previous block·next block →recent activity