← previous blocknext block →recent activity
Analyzing
Block #76,261,363
16 transactions · 12 stateful · 2026-05-22 12:30:59 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,261,363 · 16 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
12w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd784183…67bb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x24781048…4772
0x2a68ba…90c5
2 touches
0 conflicts
0x76e96198…eec4
0x2a68ba…90c5
2 touches
0 conflicts
0x120bedf0…326c
0x34b655…2a6f
2 touches
0 conflicts
0x221886a0…e130
0x34b655…2a6f
2 touches
0 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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 0xfd784183e1…ab67bb
Audit this contract →
← previous block·next block →recent activity