← previous blocknext block →recent activity
Analyzing
Block #76,444,276
14 transactions · 12 stateful · 2026-05-23 08:48:52 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,444,276 · 14 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
3w04w16w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dfb0062…8921
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe624c30a…959d
0xd32edf…ff58
3 touches
1 conflict
0x22863bf9…19df
0x34b655…2a6f
2 touches
0 conflicts
0x2d3d9bbb…4ac0
0x34b655…2a6f
2 touches
0 conflicts
0x4d75d0b3…e59c
0x34b655…2a6f
2 touches
0 conflicts
0x7cf0b873…8f7c
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x6dfb0062ad…9e8921
Audit this contract →
← previous block·next block →recent activity