← previous blocknext block →recent activity
Analyzing
Block #76,141,538
13 transactions · 11 stateful · 2026-05-21 23:13:00 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,141,538 · 13 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
1w010w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x602a6094…0644
0x34b655…2a6f
4 touches
1 conflict
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0x9e719c7a…df63
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf9a82daf…3072
0xd32edf…ff58
3 touches
1 conflict
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x1fe1380c…bf26
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0x602a609448…910644
Audit this contract →
← previous block·next block →recent activity