← previous blocknext block →recent activity
Analyzing
Block #91,423,844
14 transactions · 12 stateful · 2026-07-29 19:11:40 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,423,844 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
14 touches
21 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x177211e2…1c2d
0x754704…b603
2 touches
0 conflicts
0xe1f61186…e2f8
0x754704…b603
2 touches
0 conflicts
0x00000000…0006
0x7b9256…1fb2
2 touches
0 conflicts
0xa0dba72e…db15
0x7b9256…1fb2
2 touches
0 conflicts
0xa0dba72e…db16
0x7b9256…1fb2
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: 0x48cba278…e2b48b
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity