← previous blocknext block →recent activity
Analyzing
Block #76,530,001
9 transactions · 7 stateful · 2026-05-23 18:19:35 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,530,001 · 9 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe54a1f6f…18f2
0x34b655…2a6f
4 touches
1 conflict
0x75f6889e…7f1e
0x34b655…2a6f
4 touches
1 conflict
0x6d0c65d9…c36f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe072d43a…1835
0x34b655…2a6f
4 touches
1 conflict
0x2b856d86…7988
0x34b655…2a6f
2 touches
0 conflicts
0x33c900d4…589d
0x34b655…2a6f
2 touches
0 conflicts
0x649b200a…09a1
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 0xe54a1f6fdd…7918f2
Audit this contract →
← previous block·next block →recent activity