← previous blocknext block →recent activity
Analyzing
Block #91,085,871
10 transactions · 9 stateful · 2026-07-28 14:49:55 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,085,871 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x3ed36916…d71b
0x34b655…2a6f
4 touches
1 conflict
0x7c93b38a…9e69
0x34b655…2a6f
4 touches
1 conflict
0x70b85158…73c8
0x851145…3f07
4 touches
1 conflict
0x353231a9…1292
0xd32edf…ff58
3 touches
1 conflict
0x2650a596…a3e6
0x188d58…ea8e
2 touches
0 conflicts
0x2650a596…a3e7
0x188d58…ea8e
2 touches
0 conflicts
0x2f77f0f6…4a92
0x188d58…ea8e
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 0xf764072638…5119a2
Audit this contract →
← previous block·next block →recent activity