← previous blocknext block →recent activity
Analyzing
Block #91,078,470
11 transactions · 9 stateful · 2026-07-28 14:12:40 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,078,470 · 11 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
1w02w14w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0xf8ceaa24…6e8e
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x40681cb0…c62a
0xd32edf…ff58
3 touches
1 conflict
0xefe3a5e0…cc00
0x851145…3f07
3 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity