← previous blocknext block →recent activity
Analyzing
Block #76,091,096
13 transactions · 11 stateful · 2026-05-21 17:37:03 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,091,096 · 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
1w02w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6aabe89…92f5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbfe7fd3a…3168
0x3bd359…433a
4 touches
1 conflict
0x2d360b55…d4f5
0x80f006…d585
4 touches
1 conflict
0x2d360b55…d4f6
0x80f006…d585
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x91b2b4c7…64ca
0x57ea24…2cec
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 0xd6aabe893a…bf92f5
Audit this contract →
← previous block·next block →recent activity