← previous blocknext block →recent activity
Analyzing
Block #91,822,344
24 transactions · 22 stateful · 2026-07-31 04:37:11 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,822,344 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w19w211w113w016w117w219w320w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0xe1350502…6131
0x34b655…2a6f
6 touches
3 conflicts
0xe57ae7ed…f6da
0x34b655…2a6f
6 touches
3 conflicts
0x2003d8cf…6836
0x34b655…2a6f
4 touches
1 conflict
0x2477d0da…f68e
0x34b655…2a6f
4 touches
1 conflict
0x24e2f462…d1cc
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity