← previous blocknext block →recent activity
Analyzing
Block #91,131,079
15 transactions · 14 stateful · 2026-07-28 18:37:22 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,131,079 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w09w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0x659bd0…a9da
4 touches
1 conflict
0x00000000…0002
0x659bd0…a9da
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0x7e28e55c…d05c
0x754704…b603
4 touches
1 conflict
0xbc66586e…20fe
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity