← previous blocknext block →recent activity
Analyzing
Block #91,607,978
14 transactions · 12 stateful · 2026-07-30 10:38:50 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,607,978 · 14 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
5w06w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa279b18d…63bc
0x34b655…2a6f
4 touches
1 conflict
0xc98d2861…8f5c
0x34b655…2a6f
4 touches
1 conflict
0x4577624d…1597
0x34b655…2a6f
4 touches
1 conflict
0x2e546dd9…4c50
0x34b655…2a6f
4 touches
1 conflict
0xf248367d…cc48
0x34b655…2a6f
4 touches
1 conflict
0xdb42d6d8…5e64
0x34b655…2a6f
3 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
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: Perpl
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity