← previous blocknext block →recent activity
Analyzing
Block #91,063,096
26 transactions · 24 stateful · 2026-07-28 12:55:18 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,063,096 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w28w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
16 touches
28 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0x296b498d…22e3
0x34b655…2a6f
4 touches
1 conflict
0x2b94651b…1e3c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x5110a94f…86d1
0x34b655…2a6f
4 touches
1 conflict
0x5110a94f…86d2
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: 0x48cba278…e2b48b
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity