← previous blocknext block →recent activity
Analyzing
Block #91,763,532
18 transactions · 15 stateful · 2026-07-30 23:41:19 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,763,532 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w310w211w012w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x086f580e…090c
0x851145…3f07
6 touches
3 conflicts
0x29a5ecc7…7df7
0x851145…3f07
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd5b10148…e637
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0xfb31d278a3…299107
Audit this contract →
← previous block·next block →recent activity