← previous blocknext block →recent activity
Analyzing
Block #91,159,436
16 transactions · 15 stateful · 2026-07-28 21:00:02 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,159,436 · 16 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
1w06w07w08w19w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e183667…d0b3
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x446e2f18…f6f7
0x7b9256…1fb2
4 touches
1 conflict
0x446e2f18…f6f8
0x7b9256…1fb2
4 touches
1 conflict
0x446e2f18…f6fb
0x7b9256…1fb2
4 touches
1 conflict
0x6e183667…d0b2
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6cd707c1…0cdb
0x065c9d…c394
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: 0x7b9256fd…e21fb2
1 conflict on slot 0x6e18366731…05d0b3
Audit this contract →
← previous block·next block →recent activity